I think Rails should have a routes folder like Ember does. One file per top level resource. Our @codeschool routes file is 886 lines.
-
-
Replying to @olivierlacan
No reason you can't. It's what Shopify does. It's just Ruby.
1 reply 0 retweets 0 likes -
Replying to @sgrif
It is, but it’s not made easier by the API and was made harder by the removal of route paths in Rails 4 I think.
1 reply 0 retweets 0 likes -
Replying to @olivierlacan @sgrif
Also “value of empty folders” bla bla bla. :-)
1 reply 0 retweets 0 likes -
Replying to @olivierlacan
I think there's a reasonable discussion there. Worth opening a thread on the core mailing list if you're interested in it
1 reply 0 retweets 0 likes -
Replying to @sgrif
I feel like I should build up more of an argument before I do that. For instance, the story of how routes.rb gets split up.
1 reply 0 retweets 0 likes -
Replying to @olivierlacan @sgrif
For instance, I doubt most people would want to complicate the initial routes.rb experience with generators.
1 reply 0 retweets 0 likes
I think there's a lot of possible paths with valid arguments for each
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.