Skip to content
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

Merged
merged 45 commits into from
Jan 13, 2024
Merged

Release! #4

merged 45 commits into from
Jan 13, 2024

Conversation

yukal
Copy link
Owner

@yukal yukal commented Jan 13, 2024

2024-01-13

Refactors

  • filter-match: update logic and tests (3220500e)
  • filter-match: rename IsMatch method (bc4392c0)
  • each-match: remove deprecated eachMatch (d32baff5)

Chores

Docs

2024-01-12

New Features

  • core: implement isValid method (638e303a)
  • core: add the modifier "fields" (54903f64)
  • core: add the modifier "each" (c62d0b59)

Refactors

  • check-field: recursively unpack interface value (65e7c931)
  • range: support numeric types (f01560b8)
  • compare: invalid rule (3684f9e8)

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

Alexander Yukal added 30 commits January 10, 2024 22:03
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
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
Alexander Yukal added 15 commits January 12, 2024 20:19
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
@yukal yukal merged commit b69cca3 into main Jan 13, 2024
2 checks passed
@yukal yukal deleted the dev branch January 13, 2024 17:32
@yukal yukal added the enhancement New feature or request label Jan 14, 2024
@yukal yukal self-assigned this Jan 14, 2024
@yukal yukal added the release release label Jan 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request release release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant