Dean Karn
Dean Karn
There is a discussion here about adding the ability, haven’t had time to play around with potential solutions yet https://github.com/go-playground/validator/discussions/1232
interesting idea, let me think about the implications for a while :)
Is this the code you're having an issue with? https://github.com/aws/karpenter/blob/a87ed30c8e60d6be25ce10fb058ad66c6174edab/pkg/apis/settings/settings.go#L57 Example doesn't clearly demonstrate an issue.
@jonathan-innis can we consolidate the conversation here :) https://github.com/go-playground/validator/issues/1142
@jaimeenkpatel I would be great if the example could be simplified into one use case. I'm not 100% sue I'm growing what you want. Are you saying that you want...
Can you please post what `event` struct looks like and the validations on it. I can’t really help without it.
Hey @tiagomelo, good question. So the first `required` is applied on the array itself `[]*Address`. So ensuring there is at least one value in the array. The second `required` is...
Hey @empaguia84 it looks like your JSON does not match your Go struct definitions. The Go struct is expecting an Array of Addresses but your sending an JSON Object instead...
This is functioning correctly @Oscar-nesto . The first required, and any other tag before the dive, is applied at the slice level. After the dive the required or any other...
@yoshuawuyts I completely agree that in practice most of the time this is a sane default, I just hope that the option to tweak at this low level is not...