You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To avoid a fragmented codebase where some exceptions are handled with rescue and on_exception hook. The idea is to create a feature toggle which will forbid the usage of Micro::Case::Safe, Micro::Cases::safe_flow() and Micro::Case::Result#on_exception to ensure that will have only one way to handle exceptions, in that case, using a standard rescue statement.
Thanks, @lunks for helping me to elaborate on this idea.
The text was updated successfully, but these errors were encountered:
To avoid a fragmented codebase where some exceptions are handled with
rescue
andon_exception
hook. The idea is to create a feature toggle which will forbid the usage ofMicro::Case::Safe
,Micro::Cases::safe_flow()
andMicro::Case::Result#on_exception
to ensure that will have only one way to handle exceptions, in that case, using a standardrescue
statement.Thanks, @lunks for helping me to elaborate on this idea.
The text was updated successfully, but these errors were encountered: