EZP-31674: Make content fields value properties nullable in phpdoc #3042
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.
7.5
Currently, incorrect property types defined in PHPDoc.
For example, in "eZ\Publish\Core\FieldType\Integer\Value"
So, it's not clear for developer if this value will be 0 when not set.
And, if the developer created app-level value object following the same type, it will throw error.
TODO:
$ composer fix-cs
).