[Serializer] Harden the ObjectNormalizer#17959
Conversation
| "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.
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 |
| "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.
Then I would rather update the constraint in require-devto ~2.8,>=2.8.4|~3.0,>=3.0.4.
There was a problem hiding this comment.
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
\TypeErrors to catchable serializer exceptions.Follows #17738 and completes #17660.