We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey! Thanks for this, amazing project!
I have a small issue which I think other people will have as well, for instance, consider this struct:
type Foo struct { Foo string `yaml:",omitempty"` Bar string `yaml:"notBar"` }
If I validate it using snake case, both fields should fail, as the first will be, by default Foo and the second one is in camel case.
Foo
Would be nice if either the default name is considered or if we could disallow not naming the field.
Cheers!
The text was updated successfully, but these errors were encountered:
Hello,
I think I understand the use case, I will try to add a new option for this.
Sorry, something went wrong.
Fixed by 7b21925
No branches or pull requests
Hey! Thanks for this, amazing project!
I have a small issue which I think other people will have as well, for instance, consider this struct:
If I validate it using snake case, both fields should fail, as the first will be, by default
Foo
and the second one is in camel case.Would be nice if either the default name is considered or if we could disallow not naming the field.
Cheers!
The text was updated successfully, but these errors were encountered: