I support the overall idea. Em 15/04/2014 18:12, "Stephen Paul Weber" <[email protected]> escreveu:
> Just ran into this for the first time and thought it was worth talking > about: because models and controllers and such just live in the root > namespace, they can be shadowed when importing a gem. > > My proposal (for discussion) is that Rails could put all the app classes > inside the module that exists for the app (as defined in > config/application.rb). Autoloading, auto-lookup, etc would use the > fully-qualified name, but the unqualified name would still work everywhere > in app code because we're inside the module. Then if an overlapping name > exists in a gem we can get at it with ::Name, etc. > > Thoughts? > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
