Add the ability to choose when commands are run

[mansakondo]

Summary

By default, commands are run before existing before_action callbacks (as TurboBoost::Commands::Controller is automatically included in ActionController::Base). This PR allows configuring this behavior to have more control over when commands are run:

# config/initializers/turbo_boost_commands.rb
TurboBoost::Commands.config.tap do |config|
  config[:run_commands_before_controller_callbacks] = false
end

Then, we can include TurboBoost::Commands::Controller manually where we want it:

class ApplicationController < ActionController::Base
  before_action :action1
  before_action :action2
  before_action :action3

  include TurboBoost::Commands::Controller
end

[hopsoft]

I like this idea, but can't you achieve the same behavior by simply moving where/when you include TurboBoost::Commands::Controller? I don't think the config option is needed.

Another approach would be to use prepend_before_action in your controller(s) for any callbacks you'd like to run before TurboBoost does. Thoughts?

[mansakondo]

Thanks for taking the time to look at this.

The config option is not needed if you're ok with not including the module by default, which would require users to include it manually. Otherwise, the config option would allow users to prevent the default behavior (TurboBoost::Commands::Controller included automatically) if needed.

Using prevent_before_action instead of before_action works too, but I was hoping to find a solution that would not require users to make this change as it will be more confusing, because the actions will need to be declared in the reversed order.

Before:

class ApplicationController < ActionController::Base
  before_action :action1
  before_action :action2
  before_action :action3
end

After:

class ApplicationController < ActionController::Base
  prepend_before_action :action3
  prepend_before_action :action2
  prepend_before_action :action1
end