Return JSON objects in a wrapper object #17
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.
This pull request changes JSON objects to be returned as an instance of
text.json.JsonObjectinstead of as an associative array.In a nutshell
This makes us able to distinguish
{}from[], which previously would have both yielded an empty array:Decision to create dedicated class
We could have used StdClass like
json_decode()does but would break BC as array access does not work, yielding Cannot use object of type stdClass as array.There is, however, still some BC breaks. If you pass the returned value to a function with an array type hint, use the
+operator for a union, useis_array(), any of the array functions or rely on an assignment creating a copy, or if you useempty(), the behavior will be different!