Fix strict mode check for period after number#1009
Conversation
fixed parse of `0.` in strict mode
|
|
Please fix the blocking SonarQube issue For future reference, it's better to combine small related fixes like #1008 and #1009, to simplify review testing. |
| string = sb.toString().trim(); | ||
| if ("".equals(string)) { | ||
| throw this.syntaxError("Missing value"); | ||
| } else if (jsonParserConfiguration != null && |
|
What problem does this code solve? Does the code still compile with Java6? Risks Changes to the API? Will this require a new release? Should the documentation be updated? Does it break the unit tests? Was any code refactored in this commit? Review status Starting 3-day comment window |
|
@eleumik PR is approved, but please add unit test coverage and fix the SonarQube issues. Otherwise, I will add update the code after the merge. |
stleary
left a comment
There was a problem hiding this comment.
Open comments will be addresssed in a future commit




fixed parse of
0.in strict mode