Daniel G. Taylor

@spa5k yes this works in tests because the response writer is mutable after the body has been written, but in a real service that's not the case, you can't write...

@spa5k I think you could actually use a [response transformer](https://huma.rocks/features/response-transformers/) for this purpose as it gives you access to the Huma context *before* writing any response body. It should let...

@bioform I see two options you could use here: 1. Middleware where you use a custom `huma.Context` implementation that loads the request and response into memory before passing it on...

@baderj that is one approach you could use. What I ran into is that sometimes you configure multiple servers and sometimes even multiple DNS entries for the same server (without...

@betaprior thanks for reporting! I have not run into this, very interesting. I can definitely document it and will try to dig into the problem a bit to better understand...

@superstas I agree your interpretation of how `allOf` could work makes sense, but I don't believe that is how it is defined in the specification. Take a look at these:...

Can someone provide a complete code example to reproduce this issue?

@nunoo have you tried using [`json.Number`](https://pkg.go.dev/encoding/json#Number) in your field instead of `int64` directly? You can still provide a custom schema or transform the generated schema to mark it as a...

@betaprior I dug into this a bit. I originally thought this might be a bug but now I'm not so sure. I re-read RFC 7386 JSON Merge Patch, specifically: ```...

I tend to agree this doesn't seem possible with the standard merge-patch, however if you *always* require these fields consistently in your APIs then I would consider copying the autopatch...