Stas Afanasev

@neffsvg +1 It's kinda related to this one https://github.com/danielgtaylor/huma/issues/560

First of all, thank you, Daniel, for the quick reply and a very detailed explanation. > What do you think? Is it worth trying to dig into this further? As...

Hey @cplaetzinger I think, you can achieve it by setting `Hidden: true` for each Operation you want to skip in the generated OAS. https://pkg.go.dev/github.com/danielgtaylor/huma/v2#Operation ``` // Hidden will skip documenting...

@cplaetzinger, if I understand your idea, this is probably one way to have the only source and two different specs. Pseudo API with four endpoints. You can control which of...

I also tried to reuse this schema via registry, but no luck ```go router := chi.NewMux() cfg := huma.DefaultConfig("My API", "1.0.0") api := humachi.New(router, cfg) customHeaderSchema := cfg.Components.Schemas.Schema(reflect.TypeOf(CustomHeader("")), true, "")...

@danielgtaylor, thank you for the clarification. Yes, it is important to us to simplify our specs as much as possible by using `$ref`. I'll look deeper at the codebase and...

@danielgtaylor, an approach with a field tag looks good; I'll try implementing it in a separate commit. As for your question: > How would this get represented in the JSON...

@danielgtaylor thank you so much for the links! My understanding of the `allOf` flow was utterly wrong. The [Extending Closed Schemas](https://json-schema.org/understanding-json-schema/reference/object#extending) you mentioned explains everything. In my case, setting `additionalProperties`...