Improve JSON::ParseException message for empty string #4875
+7
−0
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
vegai
approved these changes
Aug 23, 2017
|
This is even more confusing (and wrong) as if you have incomplete json you can easily get this error in a non empty string. |
|
Oh dear. Sorry about that thumbsup :/ |
|
I understood. Until I come up with a better implementation, I will close this PR for now. |
kenta-s
deleted the
improve-json-parse-exception-message-for-empty-string
branch
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.
When
JSON::PullParsereceives an empty string, it raises aJSON::ParseExceptionwith a message like:I think it is better to tell that
JSON::PullParsegot an empty string, and that's why the exception was raised.