Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Symfony production environment, since Doctrine 3.x, cached values for 'nullable' property can be either
null
,false
ortrue
. In Doctrine 2.x, it's onlyfalse
ortrue
. When Doctrine returnsnull
for the nullable property, the required option for the field is set tofalse
.While in fact, Doctrine considers
nullable => null
asnullable => false
, thus the field should be required.To reproduce:
false
setRequired(true)
explicitly)References:
Doctrine 3.x $nullable
How Doctrine determines nullable