Fixed SF 6.3 deprecations for Normalizers #2388
Closed
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
andreicotaga
approved these changes
Jun 30, 2023
|
Please @goetas or others, could be this merged soon? It is my only deprecation warning in several projects using Symfony 6.3. I will appreciate if this get merged. Thanks for your time and dedication. |
|
@goetas please let us know if there's anything we can do to have those symfony 6.3 fixes merged |
|
Done #2392 |
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.
Classes that implement the
Symfony\Component\Serializer\NormalizerInterfacewill require the getSupportedTypes method for Symfony >= 7.0 (see here).Currently Symfony's phpunit-bridge reports deprecation messages.
I have added the required function for the FlattenExceptionNormalizer and the FormErrorNormalizer.