I want to shuffle things around so that routes and observers are loaded last, after plugins, the after_initialize callbacks, and the application initializers. Here's the problem:
1) I add a gem (has_finder) to a file in config/initializers 2) It is used in my User model 3) AR initializes my UserObserver model, which loads User, before the config/initializers run 4) BOOM, undefined method #has_finder This issue is easily worked around, but this small change in the load order makes sense to me. http://dev.rubyonrails.org/attachment/ticket/10980/load_order.diff Can anyone think of any issues? -- Rick Olson http://lighthouseapp.com http://weblog.techno-weenie.net http://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
