|
|
|
|
|
by nilliams
3521 days ago
|
|
Don't really agree - what they're doing is very different compared to what, for example Ember does (which they call 'convention over configuration'). Next's routing is much more similar to Jekyll's which quite literally is based on your filesystem file-organisation. |
|
This scheme seems to force route parameters into query parameters. Disadvantage: It's not RESTful. Advantage: Your route parameters are now named query parameters. You only handle one dict of parameters...
I'm not sure how I feel about this.