[#2140] Make FunctionalTest compatible with Response.writeChunk() #1208
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
|
@xael-fry The PR seems to be ok. Recommended to merge. |
xael-fry
approved these changes
Jan 4, 2018
|
Merged in master thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 patch updates FunctionalTest to register an onWriteChunk action on the Response objects which it creates so that controller actions which call Response.writeChunk(Object) do not fail with an unhandled exception when invoked from GET().
This patch also includes a regression test, added to FunctionalTestTest, which calls an existing controller action in Application.