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
How do I stop the resolver from diving into nested fields?
Given
type Opt[T any] struct { Val T Present bool Null bool } type MyString string func (ms MyString) Resolve(ctx huma.Context, prefix *huma.PathBuffer) []error { if ms == "" { return []error{} } return nil }
huma seems to call the Resolver implemented on both Opt and T, I'd like to be able to not execute the resolver when the value is not present.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
How do I stop the resolver from diving into nested fields?
Given
huma seems to call the Resolver implemented on both Opt and T, I'd like to be able to not execute the resolver when the value is not present.
The text was updated successfully, but these errors were encountered: