Do not serialize Request::processRequest API request #9318
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.
Otherwise when serialize=1 is set on any URL for controller or API it will fail as it would return the serialized string instead of an expected
array
orDataTable
. In the past we always had to set it manually when usingRequest::processRequest
as all GET + POST params of the initial request are forwarded to this by default. It was not clear that someone had to setserialize=0
each time one does aRequest::processRequest
.