feat: support optional parameters #11
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds support for optional function parameters in the EventQL type system. Functions can now define parameters as optional, allowing them to be called with a variable number of arguments within a specified range.
Changes
New Public API
FunArgsstructA new public type that represents function argument types with optional parameter support:
Example
Built-in functions update
The
COUNTaggregate function now supports an optional boolean parameter:PROJECT INTO { total: COUNT() } PROJECT INTO { voters: COUNT(e.data.age > 30) }Of course
COUNTparameter needs to be source-bound soCOUNT(false)will get rejected at static analysis time.