chore(deps): update module go-playground/validator to v9 #6
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/gopkg.in-go-playground-validator.v8-9.x
branch
30 times, most recently
from
e0429fc
to
0fd6610
Compare
renovate
bot
force-pushed
the
renovate/gopkg.in-go-playground-validator.v8-9.x
branch
28 times, most recently
from
2c13464
to
fae32bc
Compare
renovate
bot
force-pushed
the
renovate/gopkg.in-go-playground-validator.v8-9.x
branch
from
fae32bc
to
2994b98
Compare
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.
This PR contains the following updates:
v8.18.2->v9.24.0Release Notes
go-playground/validator
v9.24.0Compare Source
What's new?
What was fixed?
pt_BRtranslation, thanks @AGPDev for the PRunique validation, thanks @holyspectral for the PRv9.23.0Compare Source
What's new?
RegisterStructValidation, thanks @suekto-andreas for the PRv9.22.0Compare Source
What's new?
RegisterTagNameFuncdocumentation in this PR, thanks @frou for the PR!v9.21.1Compare Source
What was fixed?
Corrected some documentation in this PR and this PR; thanks @44px & @sakura1116vg for the PR's!
v9.21.0Compare Source
What's new?
Added dutch translations thanks to @wesselvanderlinden and PR #387!
v9.20.2Compare Source
What was fixed?
Corrected language package name thanks @foolin , wee #381 for details.
v9.20.1Compare Source
What was fixed?
StructFilteredCtxnot passing the context through, thanks @dvic!, see #380 for details.v9.20.0Compare Source
What's new?
Added Chinese translations, thanks @foolin! for more details foor #379
v9.19.0Compare Source
What's new?
3 new validations added:
html- This validates that a string value appears to be an HTML element tag including those described at https://developer.mozilla.org/en-US/docs/Web/HTML/Elementhtml_encoded- This validates that a string value is a proper character reference in decimal or hexadecimal formaturl_encoded- This validates that a string value is percent-encoded (URL encoded) according to https://tools.ietf.org/html/rfc3986#section-2.1for details see PR #377 Thanks @heatwole for the PR!
v9.17.1Compare Source
What was fixed
A typo in the documentation, thanks @tengis617 for the PR
v9.17.0Compare Source
Expanded
numeric&numbervalidationsIt was originally intended for these to only be used on strings, however
it makes sense to also use them if you are dealing with type
interface{}So now ints and floats return true for this validation also as they are
both numeric and a number.
v9.16.1Compare Source
What was fixed?
According to http://www.ietf.org/rfc/rfc1123.txt Hostnames are limited to letters-digits-hyphen, removing underscore as a valid character. see PR #359 for details. Thanks @jadhub for the PR! & @danielpoe for reporting.
v9.16.0Compare Source
What's new?
ginupgrade example, see #358 for details, thanks @Ashtonian for the PR!uniquetag to also cover map values, see #361 for details, thanks @jservice-rvbd for the PR!v9.15.0Compare Source
What's new
Add the following new validations:
Thanks @QuestofIranon for the PR
v9.14.0Compare Source
What's new?
Added base64url validation according to section 5 of RFC4648 Thanks @kgeorgiou for the PR!
v9.13.0Compare Source
What's New?
Added Brazilian Portuguese translations see PR #350 Thanks @afranioce
v9.12.0Compare Source
What's new?
v9.11.0Compare Source
What's new?
added a new validation
oneofthanks for the PR @ansel1see details in the PR #343
v9.10.0Compare Source
What's new?
Added new validation
hostname_rfc1123the currenthostnamevalidation is for RFC 952###I want to use the new hostname validation, but don't want to go around and change my struct tags.
No problem, just register an Alias eg.
v9.9.4Compare Source
What was fixed?
FieldWithValue=>VarWithValuev9.9.3Compare Source
What was fixed?
Update
tagCachelocking scope to allow forvalidate.Varandvalidate.VarCtxto be used from within validations functions. see #335 for details.v9.9.2Compare Source
What was fixed/updated?
Updated docs to clarify between validation tag separator or
,and or validation tag separator|v9.9.1Compare Source
What was fixed?
There was an issue checking for the end of an or validation block and when 2 consecutive
orvalidation blocks existed, it would not return an error or return an incorrect error.NOTE: This bug only affected validation with consecutive
orvalidation blocks eg.Thanks for reporting the issue @skryja, see #329 for more details
v9.9.0Compare Source
What's new?
Added map key validation support with new
keysandendkeyseg.keysmust be directly after the dive tag; this was done for efficiency to allow map keys and values to be be handled within the same range.see docs for more details.
v9.8.0Compare Source
What was added?
Added
uniquevalidation for ensuringarray|slicecontain unique values.v9.7.0Compare Source
Whats New?
Added new
isdefaulttag, essentially it's the opposite ofrequiredand only intended for specific use cases. See #299 for more details.What was fixed?
Corrected error in
fqdnwhen value is blank, see #306 for more details.v9.6.0Compare Source
What's new?
Added
hostnameandfqdnvalidations thanks to @senuphtyz and PR #298v9.5.0Compare Source
What new?
Added contextual validation support via
context.Context: thanks to @thaonx @nuxier and PR #292RegisterValidationCtx(...)RegisterStructValidationCtx(...)StructCtx(...)StructFilteredCtx(...)StructPartialCtx(...)StructExceptCtx(...)VarCtx(...)VarWithValueCtx(...)NOTE: in v10 release all old methods will be removed and only new Context methods will remain.
v9.4.0Compare Source
What's new?
FieldLevel.FieldName()andFieldLevel.StructFieldName()_examplesto avoid any potential dependencies in examples being pulled in by go tools.v9.3.6Compare Source
What was fixed?
v9.3.5Compare Source
What was fixed?
v9.3.4Compare Source
What was fixed?
no issues with validator, just updating test.
v9.3.3Compare Source
What was fixed?
v9.3.2Compare Source
What was fixed?
Corrected Namespace issue when a field within an array or map of structs causes an error, see #266
Thanks @cbandy for reporting!
v9.3.1Compare Source
What was fixed?
structonlydid not behave as expected when not accompanied by a struct validation thanks @thessem for reporting in #264 😄v9.3.0Compare Source
What was added?
alphaunicodeandalphanumunicodevalidations which are basically just unicode variants of thealphaandalphanumvalidations that were ASCII only.relates to #261
v9.2.2Compare Source
What was fixed
update cached fields to be stored in array instead of map for #260 thanks @jonmchan for reporting
v9.2.1Compare Source
What was fixed?
The
requiredtag was not correctly validating pointer fields like the old v8existstag ( see issue #142 ) was and so that bug has been corrected. thanks @codepushr for reportingrequiredtag to the restricted tags that cannot be overridden because of it's dual functionality with pointers ( thought it already was, my mistake )v9.2.0Compare Source
What's new?
Added
StructFiltered(s interface{}, fn FilterFunc)function to allow for better filtering of fields besidesStructPartialorStructExceptfor #255thanks @jawher for the idea
v9.1.3Compare Source
What was fixed?
Explicitly qualify universal-translator imports; thanks @jawher
v9.1.2Compare Source
What was fixed?
v9.1.1Compare Source
What was fixed?
iscoloralias translationrgb|rgba|len=10was missing the=10when reporting the tag in errorv9.1.0Compare Source
What's New?
🎉 This change has been a long time coming 🎉
The story so far....
A long time ago in a validator package on a github server far far away...
A request was made for allowing custom validations #174 but the evil i18n,
localization of errors, stood in our way #230. An expedition was dispatched to
search the vastness open source, but alas no suitable i18n package with correct
pluralization rules could be found; the outlook for validator seemed grim; until a
developer created an i18n and l10n helper package locales and an i18n package
universal-translator that wraps it and then jammed that functionality deep inside of validator!
So without further ado:
RegisterTranslationenlocale here; if anyone could help in adding more for other locales that would be appreciated 😄v9.0.0Compare Source
Release 9.0.0
After much work, tweaking and design updates validator v9 has been released!
It's even faster, more efficient and built for ease of use!
Quick overview of changes
documentation has been updated to reflect all of these changes, see them for more details.
ValidationErrorsis now an[]FieldErrorinstead of a map as before.existstag has been removed, nowrequiredtag handles pointer values as well.FieldError.validate.Fieldorvalidate.FieldWithValueto a struct field only, but that is not the case, any variable can be validated and so the functions have been changed to:And now what veryone wants to see, benchmarks compared to v8
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!".🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot. View repository job log here.