Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[FrameworkBundle][Serializer] Fix APC cache service name#18567
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
[FrameworkBundle][Serializer] Fix APC cache service name#18567
Uh oh!
There was an error while loading.Please reload this page.
Conversation
tgalopin commentedApr 16, 2016
@dunglas: do you know what happened after your comment:#16795 (comment) ? |
nicolas-grekas commentedApr 17, 2016
ping@wouterj |
wouterj commentedApr 17, 2016
The validator service was renamed because the Validator component switched from using their own The serializer service was added in Symfony 2.7 (refs#13107). As it directly used doctrine cache, I think it should have been named I think it makes sense to do this renaming now. Just like all other renamings, the old service should be deprecated in favor of the new service and it should be merged into master (probably 3.1). The old service should then be removed in Symfony 4. Meanwhile, a PR should be submitted to the 2.8 branch of the Standard Edition to revertsymfony/symfony-standard@0080556 This was a mistake (and it shows the need for consistency btw). |
bd84187 to7d5e658Comparetgalopin commentedApr 18, 2016
I update this PR to have the behavior@wouterj recomanded. I'm going to create the 2.8 PR. |
3c6016d to6293226Comparetgalopin commentedApr 18, 2016
I think this is ready, targeting 3.1. |
nicolas-grekas commentedApr 18, 2016
👍 for 3.1 |
wouterj commentedApr 18, 2016
Status: reviewed Looks good. Can you please also update the |
tgalopin commentedApr 18, 2016
I'll do that tomorrow. Thanks for your review! |
6293226 tod6b1f5dComparetgalopin commentedApr 19, 2016
I did the change. |
UPGRADE-3.1.md Outdated
| -`"form.type.submit"` | ||
| -`"form.type.reset"` | ||
| * The service`serializer.mapping.cache.apc` has been renamed to |
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.
[...] has been deprecated in favor of [...]
d6b1f5d to5348344Compare5348344 to88ef89cComparetgalopin commentedApr 19, 2016
I'm not sure what the PR in 2.8 should look like. Shouldn't we apply the same PR as this one on 2.8? The validator cache service was renamed in 2.8, we could rename the serializer in 2.8 too couldn't we? |
xabbuh commentedApr 19, 2016
@tgalopin It's about updating the commented config in the Symfony Standard Edition where we use the wrong service id:https://github.com/symfony/symfony-standard/blob/2.8/app/config/config_prod.yml#L8 |
dunglas commentedApr 19, 2016 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
What do you think about deprecating the class itself and recommending the PSR-6 backend instead? |
nicolas-grekas commentedApr 19, 2016
@dunglas IMHO it's too early to deprecate for 3.1, but for sure we shouldconsider deprecating once we're used to PSR-6 caching and we're sure this wouldn't prevent any valid use case (which needs some time to me to be confirmed). |
dunglas commentedApr 19, 2016
So 👍 for this change. |
tgalopin commentedApr 19, 2016
The failure is unrelated. |
xabbuh commentedApr 19, 2016
👍 |
nicolas-grekas commentedApr 19, 2016
Thank you@tgalopin. |
…me (tgalopin)This PR was merged into the 3.1-dev branch.Discussion----------[FrameworkBundle][Serializer] Fix APC cache service name| Q | A| ------------- | ---| Branch? | master or 3.0 (not sure)| Bug fix? | no| New feature? | yes| BC breaks? | no| Deprecations? | yes| Tests pass? | yes| Fixed tickets | -| License | MIT| Doc PR | -In the commitsymfony/symfony-standard@0080556, we introduced in the standard edition the usage of `serializer.mapping.cache.doctrine.apc` instead of `serializer.mapping.cache.apc` in `config_prod.yml` comments.Earlier, we introduced the validator equivalent modification (`validator.mapping.cache.doctrine.apc` instead of `validator.mapping.cache.apc`) but while we adapted the validator configuration in the FrameworkBundle in#16822, we did not adapt the FrameworkBundle configuration for the serializer.I tested the current master of symfony-standard and it's indeed failing:```[Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException]The service "serializer" has a dependency on a non-existent service "serializer.mapping.cache.doctrine.apc".```This PR renames the serializer APCu cache service name to fix this issue. However, I'm not sure when the validator cache service modification was merged and released so I'm not sure how this PR should handle this. Is this a bug? Or is this a new feature and we should trigger a depreciation but keep the service `serializer.mapping.cache.apc` usable?Commits-------88ef89c [FrameworkBundle][Serializer] Fix APC cache service name and deprecate old name
xabbuh commentedApr 22, 2016
@tgalopin Just noticed that we already have a PR for the Standard Edition (seesymfony/symfony-standard#949). So no need to do anything there. |
Uh oh!
There was an error while loading.Please reload this page.
In the commitsymfony/symfony-standard@0080556, we introduced in the standard edition the usage of
serializer.mapping.cache.doctrine.apcinstead ofserializer.mapping.cache.apcinconfig_prod.ymlcomments.Earlier, we introduced the validator equivalent modification (
validator.mapping.cache.doctrine.apcinstead ofvalidator.mapping.cache.apc) but while we adapted the validator configuration in the FrameworkBundle in#16822, we did not adapt the FrameworkBundle configuration for the serializer.I tested the current master of symfony-standard and it's indeed failing:
This PR renames the serializer APCu cache service name to fix this issue. However, I'm not sure when the validator cache service modification was merged and released so I'm not sure how this PR should handle this. Is this a bug? Or is this a new feature and we should trigger a depreciation but keep the service
serializer.mapping.cache.apcusable?