Keep track of traversed path and implement JsonPath::query_path_and_value
#77
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.
This PR makes it possible to include paths in query results.
A new
JsonPath::query_path_and_value
function is exposed to avoid breaking backwards compatibility with existing users ofJsonPath::query
. The return value is aVec<(Vec<String>, &Value)>
where theVec<String>
represents a list of traversed keys and indices to arrive at theserde_json::Value
.For example:
This implementation surely has room for optimization - I was lazy and in a hurry and just passed owned
Vec<String>
types everywhere.I am not very familiar with the more advanced features of JSON Paths, but I did verify that the implementation works correctly in basic cases (accessing object members by keys, array indexing, wildcards and such)