Feature #99
Refactor application.rb into a module for the hyperactive engine
| Status: | Closed | Start: | ||
| Priority: | High | Due date: | ||
| Assigned to: | yossarian | % Done: | 0% |
|
| Category: | Core | |||
| Target version: | wish list | |||
| Resolution: |
Description
Currently all of the application.rb code deals mostly with the hyperactive plugin itself, not with the overall app. The current setup sorta sucks because every time we add something to application.rb, it needs to be done in the main app (not the hyperactive engine), and it'll be a huge pain in the ass to develop this way once we have multiple installations running - people will upgrade and wonder "why the hell doesn't this thing work" because they won't have the proper code in their application.rb file.
The right way to deal with this is to refactor anything hyperactive-specific from application.rb and put it into a module in the engine's lib folder. See
http://www.ruby-forum.com/topic/58893
for an example of how to do this.
History
Updated by yossarian about 1 year ago
- Status changed from New to Closed
I did this a while back, but I've now moved Hyperactive out of the Engines plugin, so this ticket is now useless. Closing.