Support for custom classes for raise

[afuno]

@sunny What do you think about allowing (for example) the Rails side of the application to specify custom classes for raise that are used inside the gem?

For what? This idea came to my mind when I was trying to separate the use of Actor into services and forms. For example, there are two base classes:

class ApplicationService
  include ServiceActor::Base
end

class ApplicationForm
  include ServiceActor::Base
end

In this case, need to somehow catch errors from child classes. And now it will all be either ServiceActor::ArgumentError or ServiceActor::Failure.

Would like to prepare two custom classes on the Rails side and pass them inside the gem to ApplicationService and ApplicationForm.

[afuno]

An abstract example of what I meant:

class ApplicationService
  include ServiceActor::Base

  argument_error_class(MyCustomErrorForService::ArgumentError)
  failure_class(MyCustomErrorForService::Failure)
end

class ApplicationForm
  include ServiceActor::Base

  argument_error_class(MyCustomErrorForForm::ArgumentError)
  failure_class(MyCustomErrorForForm::Failure)
end

[afuno]

Draft: #86

[afuno]

Prototype: afuno@7bd4723

Example:

module MyCustomErrorForService
  class ArgumentError < ServiceActor::ArgumentError; end

  class Failure < ServiceActor::Failure; end
end

class ApplicationService
  include ServiceActor::Base

  define_argument_error_class(MyCustomErrorForService::ArgumentError)
  define_failure_class(MyCustomErrorForService::Failure)
end

class PayService < ApplicationService
  input :order, type: String, allow_nil: false

  play :pay_order

  private

  def pay_order
    fail!("Can't pay for an order!")
  end
end

PayService.call(order: nil)

MyCustomErrorForService::ArgumentError: The input "order" on PayService does not allow nil values

[afuno]

@sunny up 🙂

[sunny]

Added to v3.3.0 🎉