On May 5, 4:56 am, Max Schubert <[email protected]> wrote:
> With class caching on the callbacks are called and life is happy. > > I have tried a number of solutions to this for development mode: > * config.prepare_to did not work for this > * eager_load directives did not work for this > * config.after_intialize only works for initial load, fails to be > called on reloead! > * initializer did not work for this as only called once at startup > > So far the only one that works for both the initial load of > development and after reload! is called looks like this (from our > config/environments/development.rb). > > The problem of course with this code is that 1) it is horribly ugly > and 2) it undoes the whole intent of the meta-programming when in > development mode - which was to have sub-classes self-register so > that we would not have to explicitly enumerate them and worry about > forgetting to add one should we add another subclass :p. > > Any pointers / advice on how to not do it this way but have stuff work > in dev like it does in other environments (works fine with no crazy > code when class caching is true) much appreciated. A slightly less horrible variant I've used in the past is class BaseX < ... end require_dependency 'sub1' require_dependency 'sub2' which is a little bit less horrible than having a random bootstrap_x method called in funny places but doesn't solve the problem of being easy to forget to add to the list Fred > > - Max > > # XXX - workarounds for class_caching == false in development > # mode. > # > # Sources for code fixes: > # *http://blog.thefrontiergroup.com.au/2011/03/reloading-factory-girl-fa... > # *http://guides.rubyonrails.org/configuring.html > > if Rails.env.development? > > # Bootstrap classes being referenced as we use meta-programming that > # does not get called in development because class caching > # is off. Merely accessing the classes by name triggers the > # callbacks that otherwise get called immediately with class > # caching on in non-development environments. > def bootstrap_x_callbacks > X1.nil? > X2.nil? > X3.nil? > X4.nil? > X5.nil? > X6.nil? > end > > # Run once on startup after Rails environment is all warmed up and > # ready to rock. > MyApp::Application.configure do > config.after_initialize do > bootstrap_x_callbacks > end > end > > # Schedule it to be called after every reload! > ActionDispatch::Callbacks.after do > bootstrap_x_callbacks > end > > end -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
