-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Enhanced route syntax #5
Comments
rather than type definitions, we can allow arbitrary parsers. Instead of |
@gregwebs I don't quite know how @xealot implemented Improved Angular routing in a backwards compatible way but as I understand werkzeug routing, that is actually what it provides. e.g. http://werkzeug.pocoo.org/docs/routing/#custom-converters Someone noted that they didn't like the syntax, ofc. I wouldn't mind a more familiar syntax. But further than that I have no for or against the syntax as it would only be founded in what I was use to and not objectivity. |
Closing because we are moving forward with @ksperling implementation, if you need to bring any issues from this discussion over to the new implementation please make a new issue. This thread seems to have some interesting ideas... |
👍 |
wat |
Discussion on how augment route definition (regexp, optional params, constraints,...)
We should agree in the following, in no particular order:
We could use the following pull-requests as a guide:
The text was updated successfully, but these errors were encountered: