-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Serializer] Don't overwrite $format variable in DateTimeNormalizer::normalize #20216
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
Conversation
teohhanhui
commented
Oct 14, 2016
Q | A |
---|---|
Branch? | 3.1 |
Bug fix? | no |
New feature? | no |
BC breaks? | no |
Deprecations? | no |
Tests pass? | yes |
Fixed tickets | N/A |
License | MIT |
Doc PR | N/A |
317a06e
to
8bd5b0a
Compare
👍 |
1 similar comment
👍 |
Does it fix a bug? I fail to see how this is important to change; we can probably find such other examples in the codebase. |
What is the policy? I can resubmit this for master if that's better. Or I On Fri, 14 Oct 2016, 22:26 Fabien Potencier, notifications@github.com
|
@teohhanhui I'm not against this change, but this adds a lot of overhead for the core team for no actual benefit (reviewing the change to be sure it's safe, merging the PR, possible conflicts when merging old branches to newer ones, ...). So, I prefer to avoid PRs that don't really solve any issue. Doing this as part of #20217 is indeed an option, but honestly, I don't see the need for this change. |
Sometimes it's just hard to resist the urge of wanting to fix minor code So, just for the record, should minor code quality improvement PRs like On Fri, 14 Oct 2016, 23:13 Fabien Potencier, notifications@github.com
|
The issue is that we have some experience in breaking Symfony by merging apparently minor things... So we learned to be careful... |
Should I close this? |