feat(metadata/doctrine): Use Type
of TypeInfo
instead of PropertyInfo
#6979
+726
−221
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 order to anticipate the deprecation of
PropertyInfo
'sType
in favor ofTypeInfo
's one, this PR adds a new propertyphpType
(the name can be challenged) that will aim to replacebuiltinTypes
.What has been done:
ApiProperty::$phpType
property,ApiProperty::getPhpType()
, andApiProperty::withPhpType()
.PropertyInfoToTypeInfoHelper::convertTypeToLegacyTypes
to store legacy types inApiProperty::$builtinTypes
when settingApiProperty::$phpType
, this allows API Platform to work "the legacy way" while upgrading other packages.ApiProperty
to allow other API Platform packages to upgrade first.AbstractItemNormalizer
to not be dependent on the type order (type order might not be the same with these changes)PropertyTypeExtractorInterface::getType()
inDoctrineExtractor
(asgetTypes
is deprecated)api-platform/metadata
to^4.1
,symfony/property-info
to^7.1
in all packagessymfony/type-info:^7.2
inapi-platform/metadata
andapi-platform/doctrine