Cope with Validate::Tiny API change from v1.501 #3
Conversation
This file contains 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
As per GH issue zurborg#2 Validate::Tiny changed its API as from v1.501: > Object interface changed - new is now just a constructor and check is used > to do actual validation. To adapt your code, it should be enough to just > replace all Validate::Tiny->new with Validate::Tiny->check. This commit checks whether `Validate::Tiny->can('check')` and calls constructor or constructor plus 'check' accordingly.
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.
As per GH issue #2 Validate::Tiny changed its API as from v1.501:
This commit checks whether
Validate::Tiny->can('check')and calls constructor or constructor plus 'check' accordingly.