Support lambda expressions as filter arguments.#16
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
See #15
We've allowed for lambda expressions with multiple arguments. For an array input, a two-argument lambda expression is implicitly passed the item followed by the item's index in the array..
(item, index) => item.foo and index < 3.Although not used by any filters at the moment, a two-argument lambda expression would be more useful if applied to a mapping/dictionary/hash/object, as it could be passed property/value pairs, one pair for each entry in the mapping..
(key, value) => key contains 'foo' and value.bar == '42'.