Support expressions in filters (without conversion) #5434
Merged
Conversation
This file contains 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
|
https://bl.ocks.org/anonymous/raw/c15be57dd06c39b2f5b1c71b7f1dd513/ The https://bl.ocks.org/anonymous/raw/0bdb3084a58885a63f316d73bccf8030/ |
anandthakker
approved these changes
Oct 10, 2017
| t.equal(f({zoom: 0}, {properties: {x: null}}), false); | ||
| t.equal(f({zoom: 0}, {properties: {x: undefined}}), false); | ||
| t.end(); | ||
| }); |
There was a problem hiding this comment.
Let's add a test for the case where any and all are used as expressions
Prepares for expression support
jfirebaugh
force-pushed
the
expressions-filter-no-convert
branch
from
5f5b41b
to
452b92f
Compare
This was referenced Oct 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Like #5193 but continue to use the old code for non-expression filters.