-
Notifications
You must be signed in to change notification settings - Fork 274
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
Routes must have leading slash #581
Comments
Do'h. Forgot to check if it needed to be forward-ported to Dancer2. Thanks for the ticket, @racke ! |
Dancer2 requires all routes defined with via a string to begin with The requirement for a leading |
Can you imagine a situation in which a route wouldn't start with a leading |
On 05/02/2014 09:26 AM, Sawyer X wrote:
The justification in the Dancer1 patch was to use it with prefix. At any rate, it doesn't make sense to me to introduce a different behaviour between Regards LinuXia Systems => http://www.linuxia.de/ |
If the behavior in 1 is incorrect, 2 is the place to fix it. |
On 05/02/2014 09:44 AM, Sawyer X wrote:
Why not fix it in 1 as well? Regards LinuXia Systems => http://www.linuxia.de/ |
Good question. |
I think I would reformulate "If the behavior in 1 is incorrect, 2 is the place to fix it." as "If the behavior in 1 is incorrect and we only have tuits to fix it in one place, then 2 is the place to fix it." I understand that we have limited resources and we don't want to go too deep in Dancer1 salvaging. But let's also factor in the effort required, and the added value to the users. ... did I just used "added value" in a sentence? Kill me. |
I completely agree. I think you're the person in the best position to say "this doesn't add much, and it will take too much work". Trust me that we all trust you if you say that. :) |
OK, in this case we could add it to #583 and close this issue. |
We discussed this issue and decided to prevent false routes, so we can be consistent in producing routes using prefixes. |
@omar-m-othman is claiming this one. |
A leading slash should be checked here. |
A leading slash is actually already checked:
Returns the next error:
|
Please check whether false routes work in Dancer2. Even if they do, we should port the test to Dancer2.
Reference:
PerlDancer/Dancer#1020
Regards
Racke
The text was updated successfully, but these errors were encountered: