-
Notifications
You must be signed in to change notification settings - Fork 18
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
ditch the route() argument #29
Comments
I think a tiny hello world router could then become: app.router(['/', myView]) |
@yoshuawuyts what would happen when you don't specify a default, as in your hello world example? in my setup i used the last route as the default. |
👍 to both ideas |
@ahdinosaur we could just detect if an arg was passed in - right now we throw if an incorrect path is called and we don't have a default path. I kinda like having it as the first arg; not too fond of magic tailing arguments haha - much rather detect arg count haha (': |
@yoshuawuyts yeah that makes sense. my question is that if you call |
aye, so not setting a route; ( |
As @ahdinosaur pointed out to me today, the API could be a lil bit cleaner if we ditch the
route()
argument:What do people think?
The text was updated successfully, but these errors were encountered: