-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Serializer] Harden the ObjectNormalizer #17959
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
@@ -21,7 +21,7 @@ | |||
"require-dev": { | |||
"symfony/yaml": "~2.8|~3.0", | |||
"symfony/config": "~2.8|~3.0", | |||
"symfony/property-access": "~2.8|~3.0", | |||
"symfony/property-access": "~3.1", |
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.
IIUC, this is "just" to make the test pass, right? The code change itself does not need that. So, IMO, we should keep the constraint as is and tweak the test instead.
Status: needs work |
fc84692
to
5d4d0a6
Compare
Status: needs review |
You have update the minimum version required for the PropertyAccess component in the Status: Needs work |
Travis and AppVeyor not related. Ping @symfony/deciders |
@@ -27,6 +27,9 @@ | |||
"doctrine/annotations": "~1.0", | |||
"doctrine/cache": "~1.0" | |||
}, | |||
"conflict": { | |||
"symfony/property-access": ">=3.0,<3.0.4|>=2.8,<2.8.4" |
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.
Then I would rather update the constraint in require-dev
to ~2.8,>=2.8.4|~3.0,>=3.0.4
.
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.
Why? The conflict line has the same effect and works in prod too.
👍 for 3.1. The composer.json update is fine to me. |
Transform
\TypeError
s to catchable serializer exceptions.Follows #17738 and completes #17660.