json: Improve ergonomics by changing &String to &str in methods and adding Indexing #18544
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.
Working with external
Json
is pretty unergonomic right now, and has a lot of unnecessary allocations, because everything needs to be converted toString
.find
,find_path
, andsearch
now use&str
rather than&String
.Indexing can be done with
&str
anduint
, depending on whether theJson
is anObject
or aList
.[breaking-change]