You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my project, I aim to utilize the query options factories provided by Kubb to improve our management of queries and mutations. We are currently transitioning from Orval to Kubb, but we have encountered some issues that are hindering our migration.
We prefer to use the generated query options factories and directly implement the useMutation and useQuery hooks in our components. This approach would enhance our management of these hooks in the long run. However, I have discovered that when using the query options factory methods, the error is not integrated into the query options interface. As a result, the error is always of the DefaultError type, which is simply an Error object.
What version of
kubb
is running?3.3.4
What kind of platform do you use?
MacOS
How does your
kubb.config.ts
config look likeSwagger/OpenAPI file?
No response
What version of external packages are you using(
@tanstack-query
,MSW
,React
,Vue
, ...)What steps can reproduce the bug?
In my project, I aim to utilize the query options factories provided by Kubb to improve our management of queries and mutations. We are currently transitioning from Orval to Kubb, but we have encountered some issues that are hindering our migration.
We prefer to use the generated query options factories and directly implement the
useMutation
anduseQuery
hooks in our components. This approach would enhance our management of these hooks in the long run. However, I have discovered that when using the query options factory methods, the error is not integrated into the query options interface. As a result, the error is always of the DefaultError type, which is simply anError
object.How often does this bug happen?
Every time
What is the expected behavior?
No response
Additional information
https://discord.com/channels/1117538769235615835/1321868663321661571/1321868663321661571
The text was updated successfully, but these errors were encountered: