Skip to content

Commit 781ad9f

Browse files
committed
minor #15277 [Routing] Fixing some typos (ThomasLandauer)
This PR was merged into the 4.4 branch. Discussion ---------- [Routing] Fixing some typos Question: Is this rule always true?: > then ``token`` will only get the last part and the rest is matched by ``path``. Cause if Yes, the introduction doesn't make sense: > you might get unexpected results since if there's a *rule*, it's not unexpected ;-) So it would be better to explain that the *first* parameter is always greedy. Commits ------- 7749b4c Fixing some typos
2 parents 976e11a + 7749b4c commit 781ad9f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

routing.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1125,11 +1125,11 @@ A possible solution is to change the parameter requirements to be more permissiv
11251125
11261126
.. note::
11271127

1128-
If the route defines several parameter and you apply this permissive
1128+
If the route defines several parameters and you apply this permissive
11291129
regular expression to all of them, you might get unexpected results. For
11301130
example, if the route definition is ``/share/{path}/{token}`` and both
1131-
``path`` and ``token`` accept ``/``. The ``token`` only get the last path
1132-
and the rest of the match is matched by the first argument (``path``).
1131+
``path`` and ``token`` accept ``/``, then ``token`` will only get the last part
1132+
and the rest is matched by ``path``.
11331133

11341134
.. note::
11351135

0 commit comments

Comments
 (0)