@sdghchj could you please check this one out when you have some time? It would be a great addition to the tool, being able to handle generic wrapper types globally is something a lot of codebases need.

I tested locally on my project and confirmed it works great. Here's a concrete example of what it unlocks.

Context: we use a tri-state optional.Value[T] wrapper for PATCH endpoints (absent / null / present), since Go's JSON marshaller does not distinguish null from absent (undefined) fields.

Before, we had to maintain a parallel *Doc struct purely for swagger:

// PatchRequestPayloadDoc is a doc-only type used to generate correct swagger output.
// It mirrors PatchRequestPayload but replaces optional.Value[T] with *T.
type PatchRequestPayloadDoc struct {
    Date             *int64            `json:"date"`
    Status           *domain.Status    `json:"status"`
} // @name PatchRequestPayload

type PatchRequestPayload struct {
    Date             optional.Value[int64]            `json:"date,omitempty"`
    Status           optional.Value[domain.Status]    `json:"status,omitempty"`
}

...
// @Param body body PatchRequestPayloadDoc true "Patch payload"

After, with a single line in .swaggo:

replace optional.Value[$T] $T nullable:true

The real struct is used directly in the annotation, no duplicate needed:

type PatchRequestPayload struct {
    Date             optional.Value[int64]            `json:"date,omitempty"`
    Status           optional.Value[domain.Status]    `json:"status,omitempty"`
}

...
// @Param body body PatchRequestPayload true "Patch payload"

Generated output renders each field as its inner type with x-nullable: true, exactly correct. Zero optional.Value-* intermediate definitions in the spec.

Any update ? We are also looking into using optionals with swag.

^ ditto. This would be a real boon for PATCH endpoints.

Hi @sdghchj, could you please take a look ?