a) haystack operators; b) multiline queries #56
Closed
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.
@dfilatov,
a) My intent with
=/== is very simple needle/haystack string search, allowing a program using jspath to supply a concatenated list of values as a single string, into which a single property value must match. Tested with string and numeric properties, nothing more complex.This was the simple approach; the alternative is actually searching arrays provided by caller. My suggestion is to add
=/==, then later consider array search support, perhaps with an "in" operator.b) Multiline strings are allowed using a single backtick char, in es6/node 4+. My patch simply extends jspath's definition for whitespace to include newline, return, tab -shouldn't harm anything else. Writing long jspath queries is nicer now, since concatenation isn't needed so much. Really basic example-
Cheers,
Kevin-Prichard