Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HttpFoundation] BinaryFileResponse sendContent return as parent. (2.3) #17757

Merged
merged 1 commit into from
Feb 11, 2016

Conversation

SpacePossum
Copy link
Contributor

Q A
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
License MIT

BinaryFileResponse extends Response and overrides the sendContent-method. It would be nice if it also returns as the parent does, i.e. itself. This makes it easier to deal with diff. Response classes.
The other fixes are to make SCA easier. No BC-breaks AFAIK.

@xabbuh
Copy link
Member

xabbuh commented Feb 11, 2016

👍

Status: Reviewed

@fabpot
Copy link
Member

fabpot commented Feb 11, 2016

Thank you @SpacePossum.

@fabpot fabpot merged commit 120dfe4 into symfony:2.3 Feb 11, 2016
fabpot added a commit that referenced this pull request Feb 11, 2016
…parent. (2.3) (SpacePossum)

This PR was merged into the 2.3 branch.

Discussion
----------

[HttpFoundation] BinaryFileResponse sendContent return as parent. (2.3)

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| License       | MIT

`BinaryFileResponse` extends `Response` and overrides the `sendContent`-method. It would be nice if it also returns as the parent does, i.e. itself. This makes it easier to deal with diff. `Response` classes.
The other fixes are to make SCA easier. No BC-breaks AFAIK.

Commits
-------

120dfe4 sendContent return as parent.
@SpacePossum SpacePossum deleted the 2_3_BinaryFileResponse_return branch February 11, 2016 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants