We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
6.4.7
There appears to be a regression in v6.4.7 with serializing "nested" attributes with a property path.
Given a serialization config like:
App\Entity\Foo: attributes: bar.id: serialized_name: bar_id groups: ['read']
where Bar is a relation on Foo, bar_id is not serialized in in v6.4.7, but was in v6.4.6.
Bar
Foo
bar_id
No response
#52917 seems suspect to me.
The text was updated successfully, but these errors were encountered:
Yep, this was introduced in #52917, before the changes the ObjectNormalizer would access the property using the property access component:
ObjectNormalizer
symfony/src/Symfony/Component/Serializer/Normalizer/ObjectNormalizer.php
Lines 140 to 147 in 5f7ee32
But now the isAllowedAttribute() method filters out bar.id, so it never reaches that code.
isAllowedAttribute()
bar.id
cc @mtarld
Sorry, something went wrong.
Probably we are experiencing the same issue on apigee/apigee-client-php as well.
No branches or pull requests
Symfony version(s) affected
6.4.7
Description
There appears to be a regression in v6.4.7 with serializing "nested" attributes with a property path.
How to reproduce
Given a serialization config like:
where
Bar
is a relation onFoo
,bar_id
is not serialized in in v6.4.7, but was in v6.4.6.Possible Solution
No response
Additional Context
#52917 seems suspect to me.
The text was updated successfully, but these errors were encountered: