Skip to content

Conversation

@dverkade
Copy link
Member

@dverkade dverkade commented Sep 27, 2016

The front controller only accepts an HTTP response object. The front controller now has a direct dependency on the Response\Http class, which is not correct. The front controller should not care which response object will be injected only that it will adhire the ResponseInterface. So changed this constructor to accept a ResponseInterface which in di.xml is being replaced by the Response\Http class.

The front controller only accepts an HTTP response object. The front controller now has a direct dependency on the Response\Http class, which is not correct. The front controller should not care which response object will be injected only that it will adhire the ResponseInterface. So changed this constructor to accept a ResponseInterface which in di.xml is being replaced by the Response\Http class.
@vrann vrann self-assigned this Apr 12, 2017
@vrann vrann added this to the April 2017 milestone Apr 12, 2017
@vrann
Copy link
Contributor

vrann commented Apr 12, 2017

@dverkade can you please synchronize your branch with the latest develop?

@vrann
Copy link
Contributor

vrann commented Apr 12, 2017

@dverkade actually, did it with the GitHub UI

@vrann vrann closed this Apr 12, 2017
@vrann vrann reopened this Apr 12, 2017
@magento-team magento-team merged commit 2c655c3 into magento:develop Apr 13, 2017
@magento-team
Copy link
Contributor

@dverkade thank you for your contribution. Your Pull Request has been successfully merged

@dverkade dverkade deleted the patch-4 branch June 22, 2018 14:55
magento-engcom-team pushed a commit that referenced this pull request Apr 14, 2021
[Arrows] MC-41213: Update existing Magento 2.4 code to pass Insecure Function phpcs checks
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