Operations based on request content type

[csaba-veezla]

A bit more than a year ago, I asked for this feature (now it come up again):
#1491

At first, it seemed it would be done, but months later, it was closed.
Based on the comment @stijnvanhulle left, this should be an easy thing to do, but I do not see how.

So the issue:

• there is a path: /path
• it can accept multipart/form-data or application/json content type, and the 2 payload has a different schema, obviously
• based on the use case, I have to use one or the other (we could lament the backend should work differently, but that is not the case, and I have no authority over it)
• at the end of the day, I want to have 2 React hooks, useCreatePath and useCreatePathWithMultipart, and use these based on the use case

So, how can this be handled with the recommended plugin?

[stijnvanhulle]

@csaba-veezla hi, thanks for reaching out. This is indeed not that easy to do right now but to make that work we will need a breaking change. In v5 we are planning to make some breaking changes where an improvement in the clients execution is one of. Right now we are focusing on the core of v5, after that we will start working on some rewrites of how the client uses contentType and request schemas.

[csaba-veezla]

Thanks for the fast reply!

[stijnvanhulle]

@csaba-veezla we just released a new version of Kubb v5 beta 4 that contains this feature:

See https://next.kubb.dev/docs/5.x/migration-guide#multiple-content-types