Add multiple success failures types

[bvicenzo]

Allow Success, Failure, Check and Try to be multiple Types.

Closes issue: #39

This allows success or failure to be more than one type...
A real-world example of this use is an HTTP client where we want to give provide different rescues for different HTTP codes, but same treatment for any other code for the family. For example:

User::Save(attrs: { name: 'Joe' })
  .on_success(:created) { return 'User created' }
  .on_success(:ok) { return 'User Updated' }
  .on_success { return 'User Saved' }
  .on_failure(:unprocessable_entity) { |error| return "Invalid attributes #{error}" }
  .on_failure(:conflict) { return "User already exist." }
  .on_failure(:too_many_requests) { return 'You reached your limit. Try again latter' }
  .on_failure(:bad_gateway, :gateway_timeout, :service_unavailable, :internal_server_error) { |return| return 'temporary trouble. try again latter' }
  .on_failure(:client_error, :server_error) do |error|
    Sentry.capture_exception("Some unexpected client error happened: #{error}")
    return "Unknow error happened, please contact system administration"
  end

[matheusbsilva]

👏 👏 Awesome!

I have a question though, does this change breaks compatibility with the current version?

[bvicenzo]

@matheusbsilva Thanks for reviewing this ❤️

Man, the idea is to keep compatibility...

Providing just this new deprecation warning: https://github.com/Fretadao/f_service/pull/41/files#diff-53c2e1dfdeb23d78fffd5f40d1602d38df5bd3f5d9903d8ab3bcf52402bb473cR24

I've tested on some services from our Web system, and seems that it's working...

Could you test it against our Kippu system also?

Just pointing the Gemfile to this branch:

gem 'f_service', github: 'Fretadao/f_service', branch: 'bv-add-multiple-failures'

updating and run the system.

[j133y]

🥇