Question about 'required by default' about huma HOT 5 CLOSED

@jpincas there is no switch you can flip to make everything optional by default. You can add ,omitempty to all the fields and that will mark them as optional, or like you already mentioned using required:"false".

Another alternative is to provide a custom schema or use the newly released SchemaTransformer functionality to set s.Required = []string{} to undo all the required fields, see https://github.com/danielgtaylor/huma/releases/tag/v2.18.0.

If you don't want to do this for each input struct then you can also just write a function which goes over api.OpenAPI().Components.Schemas.Map() and modifies each one to set the Required slice to be empty. Hope this helps!

from huma.

Thanks Daniel. I'll experiment with those options.

from huma.

@danielgtaylor Using the api.OpenAPI().Components.Schemas.Map() iteration technique - the documentation does indeed change and none of the fields are showing as required (the effect I want to achieve), but requests are still rejected with the full list of missing required fields. Is there something else I'm missing?

from huma.

@jpincas sorry I think you may be running into https://github.com/danielgtaylor/huma/blob/main/schema.go#L280. There is some caching of required property info that should probably get recomputed after you modify s.Required. We'll need a bug fix for that.

from huma.

OK understood - thanks for your help.

from huma.