Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit b57df54

Browse filesBrowse files
committed
Reword disabled resolvers paragraph
1 parent 432c2eb commit b57df54
Copy full SHA for b57df54

File tree

1 file changed

+3
-5
lines changed
Filter options

1 file changed

+3
-5
lines changed

‎controller/value_resolver.rst

Copy file name to clipboardExpand all lines: controller/value_resolver.rst
+3-5Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -263,13 +263,11 @@ that's why we can assign ``null`` as ``$session``'s default value.
263263
We target a resolver by passing its name as ``ValueResolver``'s first argument.
264264
For convenience, built-in resolvers' name are their FQCN.
265265

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

272-
273271
Adding a Custom Value Resolver
274272
------------------------------
275273

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.