Monday, August 24, 2015
Can anyone explain this to me? If I name a project foo_bar, and use 'Rails.application' as a root for configuration paths or similar, I will end up with a cryptic error on some operations. The fix is to make all references to the application using 'FooBar::Application' in place of 'Rails.application', but what is it that makes this happen, and would there be any sense in trying to tease it out, or make a work-around configuration where you could set the expected alias once, rather than replacing the useful shortcut everywhere it is used?
-- It appears to be part and parcel with the bits of code that recognize an Engine, and namespace its operations based on the path. `/` gets changed to `_`, and then interpreted as the inverse later. Meaning is inferred where none should exist.
Walter
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/c045c5f6-462a-49e7-abd9-57e86f815b6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment