Proto multiresult periodprop cb #35
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
… false upon failure to find path (to allow distinguishing of undefined--a non-allowed JSON value--from the valid JSON, null or false) and return the exact value upon falsy single results (in order to allow return of null) * Continue work on new class-based API and object-based arguments (with option to run new queries via evaluate() method without resupplying config) * Allow new preventEval=true option * Allow new callback option to allow a callback function to execute as each final result node is obtained * Support "parent" and "parentProperty" for resultType along with "all" (which also includes "path" and "value" together) * Support "." within properties * Support custom @parent, @parentProperty, @Property (in addition to custom property @path) inside evaluations * Support a custom operator ("~") to allow grabbing of property names * Fix for @path in index/property evaluations * Expose cache on JSONPath.cache for those who wish to preserve and reuse it * Expose class methods `toPathString` for converting a path as array into a (normalized) path as string and `toPathArray` for the reverse (though accepting unnormalized strings as well as normalized) * Allow ^ as property name * Update README with more examples, APIs, and better code comments; update tests * Add tests for callback, custom properties, "all" return type, properties, return (path) type, toPath * Obscure JSON.stringify fix * Add self to contributor list
This was referenced Dec 16, 2014
Closed
This was referenced Dec 16, 2014
Merged
Merged
Merged
…ultiresult-periodprop-cb (new approach also handles periods) # Conflicts: # lib/jsonpath.js
brettz9
added a commit
that referenced
this pull request
Dec 13, 2015
Proto multiresult periodprop cb
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.
Ok, it's almost just one commit. :)
If you were looking at my previous most recent pull request, this commit builds on those with a few more changes (and a fix or two, e.g., single path result), most notably:
You also may not have noticed a couple recent additions into the previous PR:
This PR fixes issues #20, #22, #24, #34 , (and the preventEval option is an inadequate temporary replacement for #4 ).