Is it possible to generate OpenAPI schema for path parameters? I can get the validation with

Path.regex("([0-9a-fA-F])")

now, but the generated schema is just:

{
            "schema": {
              "type": "string"
            },
            "in": "path",
            "name": "hexParam",
            "required": true,
            "description": "Hexadecimal value"
          },

I would like:

{
            "schema": {
              "type": "string",
              "pattern": "[0-9a-fA-F]"
            },
            "in": "path",
            "name": "hexParam",
            "required": true,
            "description": "Hexadecimal value"
          },

unfortunately all Path parameters are created without the pattern metadata. you can mapWithNewMeta to change the type though

Any plans to fix this?

"fix". no

OK, fair enough.

Well there are nice tooling things you can do with the contracts, but if you really aren't going to use them then the standard routing is an excellent option tbh

I don't have need for standard authentication, callbacks or webhooks either.

Even if I'm not using the OpenApi generator, it's still nice because: • you get the path parameter values injected into your server handlers • you can reuse the

ContractRouteSpecX.Binder

for your clients and fakes • Even if you don't expose the spec publicly, it's still incredibly useful for documenting internal APIs