-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release! #4
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
compares the compliance between the prototype and value, the value must correspond to the specified prototype within the minimum threshold
a group of elements that contains a set of rules to check
usage within string type
it seems that reusable workflows are running slowly because of nested runners
needs golangci
compares the compliance between the prototype and value, the value must correspond to the specified prototype within the maximum threshold
compares the compliance between the prototype and value, the value must exactly equal the specified prototype
compares the match between the prototype and the value, the value must match the specified range between the minimum and maximum threshold
compares the compliance between the prototype and the value, the value must match the specified year
Validates each element of the collection using the validator filters: "each:min", "each:max", "each:eq", "each:range", "each:match". The types that this rule works with are: array, slice, map
return the error message if the specified rule is not provided
support numeric types within the validator.Rule
check the successful count of the validated fields
return boolean instead of error hints
use modifier "each" instead, example: "each:match"
IsMatch become a closed func with name filterMatch
It should be private and return an error hint with a type string. In case the value does not match, it should return "is invalid", otherwise, if an error occurs while parsing the regular expression, it should return "has an invalid rule". There is no need to check the data type of both the regular expression and the passed value because calling the reflection.String() always returns a string value without causing an error
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.
2024-01-13
Refactors
Chores
Docs
2024-01-12
New Features
Refactors
Tests
2024-01-11
New Features
Tests
Docs
Chore
Continuous Integration
2024-01-10
New Features
Tests
Docs
Chore
Continuous Integration
2024-01-09
Chore