On Wed, Dec 2, 2009 at 20:37, Jeremy Kemper <[email protected]> wrote:
> > The rails_xss plugin would need to be restructured a bit to make it > easier to explicitly require and initialize. > > Otherwise users have to explicitly config.plugins = [:rails_xss, > :will_paginate, ...] Yes, this will work for plugins, but gems are still loaded before plugins. Even if rails_xss initializer is restructured so that a simple `require 'rails_xss'` is enough, I can't do that from plugin code. How do I know if the user *wants* to load rails_xss? Maybe loading of rails_xss, being an important 3.0 feature, could be special-cased in Rails 2.3.6 loading strategy? -- 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.
