Ruona Onobrakpeya

@g4s8, I looked into this a bit and it stems from how the `FieldInfo` `Names` get generated. The [cleanenv decoding](https://github.com/g4s8/envdoc/blob/b83879d20fa2fa4b5d7a068cf5c7afabc4bb383a/field_decoder.go#L143) always sets the names to a slice which has exactly...

I just added an extra bit of customisation. Previously, the headers of the generated files were hard-coded to `Environment Variables`. In a codebase where multiple files are generated, it can...

@kyleconroy, can you please confirm if this is something worth having? We have quite a few queries which benefit from it.

Hey, @kyleconroy. 🫡 I noticed you made a push for this about a week ago. Is there something else I need to do for it to be merged into main?

The [notEmpty](https://github.com/caarlos0/env/blob/e389ab38b06e016985808dd8df2458c596bd9301/example_test.go#L70) tag does that.

Thanks, @leonklingele . The `import-require-grouping` is the closest to what I pictured, yet it enforces the opposite style. XD. I would rather have single imports be inlined. E.g. ```go import...

Does #428 help, perhaps? Overriding the `CreateHooks` of the Huma config removes the `$schema` field from responses, but not components so it might not be fully what you need.

Yes, the comments [here](https://github.com/danielgtaylor/huma/blob/df27bef3762b5e4a3f08ea767da3fa10f1f589c9/transforms.go#L36) and [here](https://github.com/danielgtaylor/huma/blob/df27bef3762b5e4a3f08ea767da3fa10f1f589c9/defaults.go#L80-L81) imply that this is meant for the response only. Though the justification for that field, > This is useful for clients to understand the...