Fix Symfony deprecation for not declaring getSupportedTypes on FlattenExceptionNormalizer #7089
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexander-schranz
requested changes
Jun 22, 2023
…tenExceptionNormalizer
alexander-schranz
force-pushed
the
normalizer-supported-types
branch
from
67dcc35
to
8dd7d91
Compare
alexander-schranz
changed the title
alexander-schranz
approved these changes
Jun 24, 2023
|
@stollr Thank you! |
|
You're welcome |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What's in this PR?
I have added a
getSupportedTypesmethod to theFlattenExceptionNormalizer.Why?
Classes that implement the
Symfony\Component\Serializer\NormalizerInterfacewill require thegetSupportedTypesmethod for Symfony >= 7.0.Currently Symfony's phpunit-bridge reports a deprecation message.
Update:
In the Symfony docs you'll find the details about that method (see here).