Manage JSON_THROW_ON_ERROR conflict #258
Closed
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.
Hi,
Consider the following code using the standard
json_decode
PHP functionIt has the expected behavior.
Now have a look at this the following code using the standard
json_decode
PHP functionIt has comes to a weird behavior.
Due to the above, the Safe\json_decode function has this bug :
This is throwing because of
json_last_error()
not being updated when usingJSON_THROW_ON_ERROR
.For the record I found this bug because of a vendor using standard
json_decode
and then me calling safe version withJSON_THROW_ON_ERROR
.