Allow to specify EntityValueResolver as ValueResolver
#1624
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
MatTheCat
force-pushed
the
entity_value_resolver-name
branch
from
7a9e475
to
909ba13
Compare
MatTheCat
force-pushed
the
entity_value_resolver-name
branch
from
909ba13
to
beac96e
Compare
stof
approved these changes
Feb 23, 2023
nicolas-grekas
approved these changes
Feb 23, 2023
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.
Follow-up of symfony/symfony#48992: a new
ValueResolverattribute can be attached to a parameter to specify which resolver will yield its value. This PR will allow to write(The used syntax allowing to add a
nameattribute to a tag has been introduced insymfony/dependency-injection5.1 by symfony/symfony#36586. This is not a problem since we require^5.4 || ^6.0.)