Adding support for custom error messages on guard functions #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates to issue #34
This commit will add the ability to declare a custom error
message for guard functions and properly propagate it.
Guard conditions will allow the transition if it returns anything other than a tuple with
{:error, "cause"}
:{:error, "cause"}
: Transition won't be allowed._
(anything else): Guard clause will allow the transition.Example:
When trying to transition an struct that is blocked by its guard clause you will
have the following return: