Dealing with handlers requiring a HandlerFunc; within ogen?

[johannes-riecken]

For health status handlers we use a company-internal library which provides a HandlerFunc.
The easiest way to make use of it is to use mux.Handle, as described in the ogen docs, but as we have the path also defined in the OpenAPI spec, ogen generates code which requires to implement the handler matching its Handler interface, and I don't see how to convert our HandlerFunc to that shape. In our OpenAPI spec, the health check follows a JSON schema, where for keys like "database" values like "OK", "WARN" and "ERROR" are possible.

Do you see a way to get around this problem? Would it make sense for ogen to add support for another annotation, something like x-ogen-ignore, to skip code generation for one path?

[tdakkota]

You can use --filter-path option to exclude some PathItems from generated code.