Setup server-side abort and error handler hooks for commands

[hopsoft]

Add's hooks to trap and handle Command aborts and errors.

Video Demo

Example

class ApplicationCommand < TurboBoost::Commands::Command
  # Abort a command from a before callback by invoking `throw :abort`
  # before_command { throw :abort }

  # NOTE: Callbacks use throw/catch to manage control flow which means
  #       this is not a real error per se, but you can intercept with rescue_from
  rescue_from TurboBoost::Commands::AbortError do |error|
    # do something...
  end

  # Setup an error handler with `on_error`
  rescue_from TurboBoost::Commands::PerformError do |error|
    # do something...
  end
end

Abort Visibility

Aborts will return an HTTP status of 285 instead of 200 along with some HTTP Headers to improve debuggability.

Error Visibility

Errors return an HTTP status of 5XX along with some HTTP Headers to improve debuggability. Error handling works if an error is raised in a Command lifecycle callback (before_command, etc.) or if raised from within the Command's perform method.

HTTP Headers

This PR introduces 2 new HTTP Headers to help with debugging.

• TurboBoost-Command - Name of the Command that was invoked
• TurboBoost-Command-Status - Status and info regarding Command invocation