@@ -790,11 +790,6 @@ concise, but it can decrease route readability when requirements are complex:
790790 // ...
791791 };
792792
793- versionadded ::5.2
794-
795- Since Symfony 5.2, inline parameter requirements are also supported in the
796- host. Before Symfony 5.2, they were supported in the path only.
797-
798793
799794~~~~~~~~~~~~~~~~~~~
800795
@@ -989,11 +984,6 @@ parameter:
989984 To give a ``null `` default value to any parameter, add nothing after the
990985 ``? `` character (e.g. ``/blog/{page?} ``).
991986
992- ..versionadded ::5.2
993-
994- Since Symfony 5.2, inline parameter default values are also supported in
995- the host. Before Symfony 5.2, they were supported in the path only.
996-
997987Priority Parameter
998988~~~~~~~~~~~~~~~~~~
999989
@@ -2046,6 +2036,16 @@ these routes.
20462036 // ['HTTP_HOST' => 'm.' . $client->getContainer()->getParameter('domain')]
20472037 );
20482038
2039+ ..tip ::
2040+
2041+ You can also use the inline defaults and requirements format in the
2042+ ``host `` option: ``{subdomain<m|mobile>?m}.example.com ``
2043+
2044+ ..versionadded ::5.2
2045+
2046+ Inline parameter default values support in hosts were introduced in
2047+ Symfony 5.2. Prior to Symfony 5.2, they were supported in the path only.
2048+
20492049.. _i18n-routing :
20502050
20512051Localized Routes (i18n)