We're seing annoying deprecation warnings despite the fact that we do not use caching at all (it's disabled in an initialiser).
In prior Rails versions, it used to be more challenging to create a stand-alone application without the entire file structure of Rails surrounding it, which is why the spec/dummy was in here in the first place. This is no longer the case, and this change removes the dummy app in favor of a smaller set of files which achieve the same result of providing a small footprint Rails app which the test suite can load the gem into, and run tests against an actual Rails app.
Allow a user to define which Rails engine to define routes on when using multiple engines within a Rails application. This will ensure that path helpers will correctly be available in the desired engine. This will default to the default main Rails application if another engine is not specified. Resolves issue [#138](#138)
`#concern_reload` would execute the Rails `caches_page` and `caches_action` methods multiple times resulting in multiple callbacks being associated with the controller. This lead to inconsistencies. Instead `config.action_controller.perform_caching` is now set to true by default. With this in place we no longer need to reopen the class in order to test caching. Refactor `action_caching` spec to test via spying rather than testing caching directly. Now that we are no longer actually caching items, we no longer need to clear the cache via `ActionController::Base.cache_store.clear`.
high_voltage.rb uses mattr_accessor methods, which are provided by active_support. Normally these methods are provided by having Rails ran beforehand, but this meant that high_voltage couldn't be loaded alone. Added necessary require to address this.