-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
24773 deprecation of getrequestformat #25213
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
24773 deprecation of getrequestformat #25213
Conversation
Given that stable release of Symfony 3.4 and 4.0 is tomorrow, this is far too late to add a new deprecation in it. So I changed the target to master |
referencing your own PR in |
@@ -196,7 +196,7 @@ class Request | |||
/** | |||
* @var string | |||
*/ | |||
protected $format; | |||
protected $requestedResponseFormat; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renaming a protected property is a BC break. This is not allowed. See https://symfony.com/doc/current/contributing/code/bc.html for details about which kind of changes are allowed or no to respect the BC policy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will revert that.
Status: needs work |
Updated above link, it was meant to point to the issue not my own PR, that was very strange. Reverted rename of protected $format. |
Status: Needs review |
I am investigating the break on 7.2 |
I'm closing here as this didn't get much traction: renaming methods needs a clear benefit, so that the extra work we put on devs is justified. it doesn't feel the case here. |
Uh oh!
There was an error while loading. Please reload this page.