@@ -322,7 +322,7 @@ this argument) or an array with the resolved value(s). Usually arguments are
322
322
resolved as a single value, but variadic arguments require resolving multiple
323
323
values. That's why you must always return an array, even for single values::
324
324
325
- // src/ValueResolver/IdentifierValueResolver .php
325
+ // src/ValueResolver/BookingIdValueResolver .php
326
326
namespace App\ValueResolver;
327
327
328
328
use App\IdentifierInterface;
@@ -374,6 +374,20 @@ but you can set it yourself to change its ``priority`` or ``name`` attributes.
374
374
375
375
.. configuration-block ::
376
376
377
+ .. code-block :: php-attributes
378
+
379
+ // src/ValueResolver/BookingIdValueResolver.php
380
+ namespace App\ValueResolver;
381
+
382
+ use Symfony\Component\DependencyInjection\Attribute\AsTaggedItem;
383
+ use Symfony\Component\HttpKernel\Controller\ValueResolverInterface;
384
+
385
+ #[AsTaggedItem(name: 'booking_id', priority: 150)]
386
+ class BookingIdValueResolver implements ValueResolverInterface
387
+ {
388
+ // ...
389
+ }
390
+
377
391
.. code-block :: yaml
378
392
379
393
# config/services.yaml
@@ -455,7 +469,7 @@ As an alternative, you can add the
455
469
:class: `Symfony\\ Component\\ HttpKernel\\ Attribute\\ AsTargetedValueResolver ` attribute
456
470
to your resolver and pass your custom name as its first argument::
457
471
458
- // src/ValueResolver/IdentifierValueResolver .php
472
+ // src/ValueResolver/BookingIdValueResolver .php
459
473
namespace App\ValueResolver;
460
474
461
475
use Symfony\Component\HttpKernel\Attribute\AsTargetedValueResolver;
0 commit comments