-
-
Notifications
You must be signed in to change notification settings - Fork 895
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
V3.2.20 Did Not Fix The BackedEnum Serialization Priority Error #6285
Comments
# config/services.yaml
serializer.normalizer.backed_enum:
class: Symfony\Component\Serializer\Normalizer\BackedEnumNormalizer
tags:
- { name: 'serializer.normalizer', priority: -891 } Any priority from -891 and lower fixes the problem. |
In my case, the GraphQL normalizer is not even listed.
|
Related to #6279 |
Closing as not an API Platform bug, hopefully this gets fixed in Symfony. |
nicolas-grekas
added a commit
to symfony/symfony
that referenced
this issue
Apr 4, 2024
… translatable (GwendolenLynch) This PR was squashed before being merged into the 6.4 branch. Discussion ---------- [Serializer] reset backed_enum priority, and re-prioritise translatable | Q | A | ------------- | --- | Branch? | 6.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | Fix #54478 Fix api-platform/core#6285 Fix api-platform/core#6279 | License | MIT - `serializer.normalizer.translatable` -920 (was -890) - `serializer.normalizer.backed_enum` -915 (originally -915, changed to -880) Floating this as as solution to the knock-on issues from #54478 Context: - #54478 (comment) - api-platform/core#6288 Commits ------- b559aa5 [Serializer] reset backed_enum priority, and re-prioritise translatable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
API Platform version(s) affected: 3.2.20
Description
Refer to symfony/symfony#54478.
I do not use GraphQL, and the issue still exists in 3.2.20.
The only work-around I can find is to hack the priority in
services.yaml
.How to reproduce
Here is a repository with a problem replicator.
Possible Solution
Additional Context
The text was updated successfully, but these errors were encountered: