You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
There is a specific use-case that does not seem to be handled correctly by the flow controller: when a place name consists of just a place parameter (e.g. :some-param) it will match any URL that consists of a single path segment (good), but it will match neither empty URLs nor URLs consisting of just a slash.
This behavior is inconsistent with place definitions that do have a constant prefix. These do match URLs with an empty trailing parameter segment.
The text was updated successfully, but these errors were encountered:
x1B
changed the title
flow: (v2.x) place with parameter, but without constant prefix does not match empty path
flow: (v2.x) place with parameter, but without constant prefix, does not match empty path
Nov 7, 2016
Ok, the reason is that some of the regular expressions used in route parameter matching are too specific, demanding a slash before each parameter's colon.
There is a specific use-case that does not seem to be handled correctly by the flow controller: when a place name consists of just a place parameter (e.g.
:some-param
) it will match any URL that consists of a single path segment (good), but it will match neither empty URLs nor URLs consisting of just a slash.This behavior is inconsistent with place definitions that do have a constant prefix. These do match URLs with an empty trailing parameter segment.
The text was updated successfully, but these errors were encountered: