cgen, json: make errors more informative (resolve empty panics) #22898
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.
The changes make error messages for
json.decode
more informative. The reason is that error messages we'll get when walking back on the cJSON error_ptr can currently be empty and become hard to localize. The example below would currently just print an empty line.With the changes the errors message
failed to decode JSON string
is added. Similar tofailed to open file
during aos.read_file
error.This should help with the first of the two problems initially attempted to solve in #21184.
The second example in the linked PR could be addressed in a separate PR, where cgen is extended to add a check to verify the variable that should be decoded for validity.
Huly®: V_0.6-21341