-
Notifications
You must be signed in to change notification settings - Fork 192
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
Ugly named route group '/' urls #130
Comments
Why not we can remove it. I will mark this as a bug. So, we can work on
|
I think this is not about that. We need to keep it as like that. |
yes, when building a path, we can remove the last / and it fill be fine |
Okay, got it. |
@lmacsen hi, why do you suggest it be optional? The urls look ugly, unfriendly and leave a feeling of something unfinished. I really don't know, who and why would use trailing slashes. The choice is ok, but I don't think we need it. |
@lmacsen we are not changing the url behaviour in the browser, only the generated link path (in So, the links |
Trailing slashes seem like they are still a problem. I have a route that redirects to another route using the route name and it appends slashes at the end. FlowRouter.route('/otherroute/:param1?/:param2?', {
name: 'otherroute',
action: function () {
// Do something...
}
});
FlowRouter.route('/', {
name: 'home',
action: function () {
FlowRouter.go('otherroute');
}
}); I think it has to do with those optional params. |
@rclai It isn't directly related to this bug. Can you create separated issue? |
Example: user group routes (named)
Now we want a link for a named route
The route for the / action will be:
The last / is very ugly, can we remove it?
The text was updated successfully, but these errors were encountered: