The panels hooks/extensions rely heavily on alias_method_chain. I'm using rack-bug in a Sinatra app and I created a Sinatra Templates panel (http://github.com/iamteem/rack-bug). The app works fine because I basically added alias_method_chain in the app. However, when running rake spec, my solution fails with a NoMethodError (alias_method_chain). What's the best way to go about this depedency? Should alias_method_chain be removed from rack-bug? Or make activesupport a dependency? Or should alias_method_chain be added to rack-bug's source?
The panels hooks/extensions rely heavily on alias_method_chain. I'm using rack-bug in a Sinatra app and I created a Sinatra Templates panel (http://github.com/iamteem/rack-bug). The app works fine because I basically added alias_method_chain in the app. However, when running
rake spec, my solution fails with a NoMethodError (alias_method_chain). What's the best way to go about this depedency? Should alias_method_chain be removed from rack-bug? Or make activesupport a dependency? Or should alias_method_chain be added to rack-bug's source?