Delete path from JSON #3
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
dselans
reviewed
Dec 29, 2023
| let key_start = match find_key_start(value_begin, key, json.as_bytes()) { | ||
| Some(x) => x, | ||
| None => { | ||
| return Err(GJSONError { msg: "could not find key".to_string() }) |
There was a problem hiding this comment.
If the path is not found, the "could not find key" err is bubbled up to the SDK?
There was a problem hiding this comment.
Yes, it will return the error in the wasm response to the SDK
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.
gjson::get()intogjson::get_with_key()which returns a tuple now that includes the json keydelete_path()