8000 [HttpKernel] Document `#[ValueResolver]` and `#[AsTargetedValueResolver]` by MatTheCat · Pull Request #17763 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

[HttpKernel] Document #[ValueResolver] and #[AsTargetedValueResolver] #17763

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jun 15, 2023
Merged

[HttpKernel] Document #[ValueResolver] and #[AsTargetedValueResolver] #17763

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
7fc8065
Document https://github.com/symfony/symfony/pull/48992
Feb 28, 2023
50450a4
Address https://github.com/symfony/symfony-docs/pull/17763#discussion…
MatTheCat Apr 21, 2023
1009ca2
Do not hardcode priorities
MatTheCat Jun 4, 2023
31edf49
Fix code samples
MatTheCat Jun 4, 2023
ac13dfc
Update “Managing Value Resolvers” section
MatTheCat Jun 4, 2023
432c2eb
Remove “pin” usage remnants
MatTheCat Jun 4, 2023
b57df54
Reword disabled resolvers paragraph
MatTheCat Jun 4, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Reword disabled resolvers paragraph
  • Loading branch information
@MatTheCat
MatTheCat committed Jun 4, 2023
commit b57df5476580bfcaf5ab4903c4545eb08a8e52b0
8 changes: 3 additions & 5 deletions controller/value_resolver.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -263,13 +263,11 @@ that's why we can assign ``null`` as ``$session``'s default value.
We target a resolver by passing its name as ``ValueResolver``'s first argument.
For convenience, built-in resolvers' name are their FQCN.

The ``ValueResolver`` attribute can also be used to disable the targeted resolver
by passing its ``$disabled`` argument to ``true``, in which case it won't be called.
This is how :ref:`MapEntity allows to disable the EntityValueResolver
for a specific controller <doctrine-entity-value-resolver>`.
A targeted resolver can also be disabled by passing ``ValueResolver``'s ``$disabled``
argument to ``true``; this is how :ref:`MapEntity allows to disable the
EntityValueResolver for a specific controller <doctrine-entity-value-resolver>`.
Yes, ``MapEntity`` extends ``ValueResolver``!


Adding a Custom Value Resolver
------------------------------

Expand Down
0