How do I stop the resolver from diving into nested fields?

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 issue names no repository files or tests. Start by tracing resolver dispatch for the Opt and MyString examples, then verify how nested fields are handled when Opt is not present; done means the nested resolver is not executed for that absent value.

Written by the indexing model from the issue text.