-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating a direct link after a substitution link does not result in match #18
Comments
Hello @robdoesstuff 👋 Can you clarify your post. Here is the config and result as I understood it. This config...
Would result in this...
|
It's been a while but I do not believe that's the result I got. It seems like we have some hyphen-slash substitution happening and any go/logs/anything or go/logs-anything will match the shorter go/logs rule and not the go/logs-otherthing rule. Perhaps this isn't a problem anymore, I'm not sure. I can see if I can retest this in our deployment. |
ok and just to make sure, what release are you on? |
Here is the relevant code path in
|
If I make a link like go/logs with a %s to capture the rest so that a general go/logs/mything translates to a URL with mything substituted in, then I create go/logs-otherthing, going to go/logs/otherthing still matches the first logs go link. It should have the opposite sort where the more specific matches come first and the general are the defaults if there is no other match. This allows me to setup a catch all link then overrides with more specific urls, such as in the case of navigating to customized dashboards, logs, etc.
The text was updated successfully, but these errors were encountered: