ditch the route() argument

[yoshuawuyts]

As @ahdinosaur pointed out to me today, the API could be a lil bit cleaner if we ditch the route() argument:

app.router('/404', [
  ['/', myView],
  ['/404', defaultView],
  ['/foo', myFooView, [
    ['/bar', myOtherView],
    ['/baz', yetAnotherView]
  ]]
])

What do people think?

[yoshuawuyts]

I think a tiny hello world router could then become:

app.router(['/', myView])

[ahdinosaur]

@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.

[timwis]

👍 to both ideas

[yoshuawuyts]

@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 (':

[ahdinosaur]

@yoshuawuyts yeah that makes sense. my question is that if you call sheetRouter with a single routes argument, what is the default? i see you set dft to '', does that mean the root path (/) is the default? or does it throw if no other path matches like you say? happy with whatever, just want to make sure i understand what the behavior is.

[yoshuawuyts]

aye, so not setting a route; ('' or w/e) should make paths throw. Not sure if you can set / to be the default path (oops), but at least yeah that's the idea