Throw exception when field type is incorrect #60
Merged
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.
Another late addition to our improvements on error handling (#53).
Fixes the following edge cases:
"op"
field is booleantrue
, it is interpreted as an"add"
operation instead of throwing an exception. This is due totrue
always matching the first [switch case] (Add::OP
)."op"
field is an Array (list) or Object, it results in a "PHP Notice Array/Object to string conversion" in the [UnknownOperationException
]"path"
or"from"
fields are not a string, an exception will be thrown inJsonPatch::apply()
rather thanJsonPatch::import()