Separate openAPI generation from the schema validation

[Mael-Abgrall]

Hey folks

Is there a way to separate the open API generation and the schema validation?

• First because I'm not necessarily a fan of having the two together (validation =/= documentation)
• Second, because I'm using typebox (Using Typebox in v1 doesn't work without installing @valibot/to-json-schema #159) and I'm using the typebox validator (tValidator), which doesn't need that library.

I managed to find that body definition is possible through requestBody AND typebox schemas, but I have not found any way to do this for query or path parameters (there is no documentation around it)...

Hence, the question: would it be possible to either have two packages (one for validation, one for documentation) or allow the possibility to use the full openAPI specification independently from the validation?

[Andrew-Chen-Wang]

I've continued development here until these bugs are resolved and better support for typebox is made. Eventually it'll include some bugs I've previously noticed like OpenAPI 3 incompatibilities

https://www.npmjs.com/package/hono-typebox-openapi

[jsanchezba]

I'll probably use your package meanwhile. I tried using this for the describeRoute (Does fill the query params on the Scalar UI), but the validator itself

Hey folks

Is there a way to separate the open API generation and the schema validation?

* First because I'm not necessarily a fan of having the two together (validation =/= documentation)

* Second, because I'm using typebox ([Using Typebox in v1 doesn't work without installing @valibot/to-json-schema #159](https://github.com/rhinobase/hono-openapi/issues/159)) and I'm using the typebox validator (tValidator), which doesn't need that library.

I managed to find that body definition is possible through requestBody AND typebox schemas, but I have not found any way to do this for query or path parameters (there is no documentation around it)...

Hence, the question: would it be possible to either have two packages (one for validation, one for documentation) or allow the possibility to use the full openAPI specification independently from the validation?

I tried using the params like this, it does fill the query params on the Scalar UI, but couldn't make the validator work anyway:
Or just use a single schema for each param

        parameters: [
            {
                in: 'query',
                name: 'id',
                schema: ParamSchema.properties.id,
            },
            {
                in: 'query',
                name: 'name',
                schema: ParamSchema.properties.name,
            },
            {
                in: 'query',
                name: 'email',
                schema: ParamSchema.properties.email,
            },
        ],

I'll use @Andrew-Chen-Wang package meanwhile so I do not have to change that much code in the future.

[MathurAditya724]

@Mael-Abgrall Are you talking about generating the json separately, instead of generating them from the endpoint?

You can checkout this discussion - #168 (comment)

Or in docs - https://honohub.dev/docs/openapi/persisting