From 69e60a911d635d5835ba0b2227ba1499d6a14817 Mon Sep 17 00:00:00 2001 From: Bastian Waidelich Date: Fri, 11 Oct 2024 10:11:17 +0200 Subject: [PATCH] TASK: Tweak attribute routing docs --- .../Documentation/TheDefinitiveGuide/PartIII/Routing.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/Neos.Flow/Documentation/TheDefinitiveGuide/PartIII/Routing.rst b/Neos.Flow/Documentation/TheDefinitiveGuide/PartIII/Routing.rst index 7821c8aac8..e32a087139 100644 --- a/Neos.Flow/Documentation/TheDefinitiveGuide/PartIII/Routing.rst +++ b/Neos.Flow/Documentation/TheDefinitiveGuide/PartIII/Routing.rst @@ -749,8 +749,8 @@ It also is possible to specify a `providerFactory` and (optional) `providerOptio You can use the ``flow:routing:list`` command to list all routes which are currently active, see `CLI`_ -Subroutes from Annotations --------------------------- +Subroutes from Attributes +------------------------- The ``Flow\Route`` attribute allows to define routes directly on the affected method. (Currently only ActionController are supported https://github.com/neos/flow-development-collection/issues/3335) @@ -774,8 +774,7 @@ The ``Flow\Route`` attribute allows to define routes directly on the affected me } } -To find the annotation and tp specify the order of routes this has to be used together with the -`\Neos\Flow\Mvc\Routing\AttributeRoutesProviderFactory` as `providerFactory` in Setting `Neos.Flow.mvc.routes` +In order to make attribute routes discoverable and to specify their order relative to explicitly configured routes, the `providerFactory` has to be specified in Setting `Neos.Flow.mvc.routes`: .. code-block:: yaml