[DI] [Controller] Add controller redirect response code configuration option #1101
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.
2.0
This PR re-adds the
liip_imagine.controller.redirect_response_code
configuration option originally merged into1.0
(as #970) but never merged into2.0
.Introduces a new
Liip\ImagineBundle\Config\Controller\ControllerConfig
service that is passed as the forth argument toLiip\ImagineBundle\Controller\ImagineController
. Not passing an instance of the newControllerConfig
object will now throw a deprecation message and the ability to not do so will be removed in3.0
.The
ControllerConfig
object will also reject non-redirect HTTP codes; the configured code must be one of201
,301
,302
,303
,307
, or308
(otherwise an invalid argument exception will be thrown).See #1011 (comment) and its following conversation for more context on the missing PRs from
2.0
that were already merged into1.x
.