[symfony#14671] Added example of inline host defaults/requirements

wouterj · wouterj · commit 1ae411bfcd84 · 2020-12-09T11:39:05.000+01:00
diff --git a/routing.rst b/routing.rst
@@ -790,11 +790,6 @@ concise, but it can decrease route readability when requirements are complex:
             // ...
         };
 
-.. versionadded:: 5.2
-
-    Since Symfony 5.2, inline parameter requirements are also supported in the
-    host. Before Symfony 5.2, they were supported in the path only.
-
 Optional Parameters
 ~~~~~~~~~~~~~~~~~~~
 
@@ -989,11 +984,6 @@ parameter:
     To give a ``null`` default value to any parameter, add nothing after the
     ``?`` character (e.g. ``/blog/{page?}``).
 
-.. versionadded:: 5.2
-
-    Since Symfony 5.2, inline parameter default values are also supported in
-    the host. Before Symfony 5.2, they were supported in the path only.
-
 Priority Parameter
 ~~~~~~~~~~~~~~~~~~
 
@@ -2046,6 +2036,16 @@ these routes.
             // ['HTTP_HOST' => 'm.' . $client->getContainer()->getParameter('domain')]
         );
 
+.. tip::
+
+    You can also use the inline defaults and requirements format in the
+    ``host`` option: ``{subdomain<m|mobile>?m}.example.com``
+
+.. versionadded:: 5.2
+
+    Inline parameter default values support in hosts were introduced in
+    Symfony 5.2. Prior to Symfony 5.2, they were supported in the path only.
+
 .. _i18n-routing:
 
 Localized Routes (i18n)
