[PropertyInfo][Serializer] Add limited generics support to PhpStanExtractor
#47556
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.
This PR aims to provides a limited support of generics serialization with the help of
PhpStanExtractor
.Basically achieving:
It introduces an internal
normalization_outer_class_property
key in the normalization context to provide the property extractor the type found in the generic.Its keeping BC with iterables types documented as generics (e.g.
array<>
,Collection<>
)It's an early stage feature as generics can be very flexible and I encourage everyone to please test it on their own projects and help me catch all the remaining use cases.
It's limited in the sense that it doesn't support:
@implements Collection<T>
Debatable topics:
normalization_outer_class_property
key naming@var
type will take precedence over@param
type.To Do