One of the handy things missing from Rails, that the engines plugin
tries to provide but which isn't really core to its functionality, is
a way of inspecting the set of loaded plugins while the application is
running.
This is achieved via the Engines.plugins method (which is again
aliased as Rails.plugins, for backwards compatibility). We use this
mostly when dealing with public assets from within plugins, but it's
also useful for generating RDoc for plugins.
In fact, the only thing the custom engines plugin loader does is to
add plugins to this set, so if Rails itself implemented it, we could
simplify the plugin greatly. Maybe even get rid of the 'boot' line,
which needs to be added to the top of environment.rb!
Here's my ticket, hidden under the guise of being about the plugin
documentation task: https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2526-generated-plugin-rdoc-should-include-all-code-within-plugin-load_paths
Feedback appreciated,
James
_______________________________________________
Engine-Users mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
