This repository has been archived by the owner on Jan 8, 2020. It is now read-only.
Prevent fatal error in JsonRpc-Client #5956
Closed
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
Ocramius
added a commit
that referenced
this pull request
Apr 3, 2014
gianarb
pushed a commit
to zendframework/zend-json
that referenced
this pull request
May 15, 2015
gianarb
pushed a commit
to zendframework/zend-json
that referenced
this pull request
May 15, 2015
…r-options-enforced-as-array' Close zendframework/zendframework#5956
gianarb
pushed a commit
to zendframework/zend-json
that referenced
this pull request
May 15, 2015
…r-options-enforced-as-array' into develop Close zendframework/zendframework#5956
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Zend\Server\Json\Response passes the json_decode()'d server response to its method setOptions(), which is type hinted as array. If the server response is anything but an array, this leads to a fatal error.
Maybe the Response class should be altogether more strict in its parsing of the response, but for now I just throw a RuntimeException, as pretty much anything is preferable to a fatal error.