REALLY?? *facepalm* Not sure what this is solving. RT @steveklabnik: What’s New In Edge Rails: Routing Concerns: https://github.com/rails/rails/commit/0dd24728a088fcb4ae616bb5d62734aca5276b1b#commitcomment-1743800 …
-
-
Replying to @coreyhaines
@coreyhaines@steveklabnik Is this to avoid [:resource1, ... :resourcesN].each{ |r| resources r { resources :concern_resource } } ?1 reply 0 retweets 0 likes -
Replying to @codeodor
@codeodor I hope you wouldn't do that.@steveklabnik2 replies 0 retweets 0 likes -
Replying to @coreyhaines
@coreyhaines And trying to understand if this is simply to DRY child routes that apply across multiple parents@steveklabnik2 replies 0 retweets 0 likes
Replying to @codeodor
@codeodor @coreyhaines basically yes. traits, in a way
5:05 PM - 21 Aug 2012
0 replies
0 retweets
0 likes
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.