Closed
Conversation
added 8 commits
April 19, 2017 11:51
Codecov Report
@@ Coverage Diff @@
## master #11 +/- ##
==========================================
- Coverage 99.1% 94.59% -4.51%
==========================================
Files 22 23 +1
Lines 668 740 +72
==========================================
+ Hits 662 700 +38
- Misses 6 40 +34
Continue to review full report at Codecov.
|
|
👍 This was actually the approach I took on my first stab at it. This way feels less hacky to me and a lot cleaner. I am moving forward on unit tests on #10, I think they'll be pretty interchangeable with either approach. |
Owner
Author
|
Closing out as stale. Happy to revisit this if this functionality would be useful. cc/ @davesims |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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