WIP: Conditional exception validations #11
Closed
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.
Taking inspiration from #10 I wanted to see how it felt maintaining two sets of validation methods and invoke them at the
ActionLogic::ActionCorelevel.I also took inspiration from
ActiveModel::Errorsso if the non-bang validation method is used and errors are found,ActionLogicprovides acontext.errors.messagesinterface:I've updated the three types of validations (Attribute, Presence and Type) to support this difference, and am still working through updating the tests and fixtures.
My goal isn't to replace #10 but to compare approaches and see if some mix and match would be ideal, or if we like one direction or the other.
/cc @davesims