Dean Karn

@emirefek I would file a bug with the official Golang plugin and/or VSCode. I haven't used VSCode for a few years now but know for a fact it shouldn't be...

@maocatooo unfortunately there is no automated way to achieve what you're looking for as validator is designed to return only the first failed validation, per field, and changing the package...

@navamedha TY for the PR. Now that validation tags run properly on structs themselves this is something I've been thinking about adding. This is a variant, one of many, I've...

Sorry all, not sure when I am going to be able to get to this and many other PR’s as I am swamped with other projects at the moment. I...

Thanks fro the PR @darklam I will have to think hard on if this could cause any breaking side-effects, see [here](https://github.com/go-playground/validator/issues/907#issuecomment-1849000624) for details.

Hey @fizzy123 this will work if you use `required_without_all` it looks like some of the docs have been copy-pasted and are not 100% correct. I could use some help with...

I will need to think about this, again, as in the documentation I explicitly state why I do not already have a `regex` validation, but to summarize a few points:...

@yousifnimah yep I understand and makes sense. You can also do this today by registering a custom validation with tag that uses the Regex internals which may be more maintainable....

Are you sure you read the documentation? https://pkg.go.dev/github.com/go-playground/validator/v10#hdr-Universally_Unique_Identifier_UUID The docs clearly state the uuid validation is for strings. I have to assume the pgtype.UUID is this one, because the example...

Please see https://github.com/go-playground/validator/issues/1157 This was thoroughly discussed in https://github.com/go-playground/validator/issues/1142 originally. The TL;DR is that struct validations were not running as expected prior to this change. This is a correction of...