Typescript client not working when fastapi responses are in camelCase about openapi-ts HOT 6 CLOSED

Hey @vinod-canihelp, let's start with your OpenAPI spec and are you able to provide either a reproducible example or a screenshot of the issue?

from openapi-ts.

afaik, the openAPI spec looks good. The types generated are correct.
Let me create small reproducible example in an hour and share.

from openapi-ts.

Something's fishy... I have 4 APIs. All 4 APIs give camelCase response using curl.
However, two of the APIs give camelCase response using hey-api fetch client while the other two doesn't. Makes no sense. Digging deeper.

If there's an option to log stuff inside the client, it would be very helpful. Let me know if that's an option.

from openapi-ts.

I have a NextJS app for frontend. When the API is called from the nextjs client side code, the api response is camelCase. But when the same API is called from nextjs server side code, the api response is snake_case!!!

from openapi-ts.

Found the issue. Stale data was cached somewhere. Clearing browser cache and reloading fixed the issue.

Hey @mrlubos! First, I apologize for reporting a wrong bug. Second, is there a recommended way to set cache policy or time-to-live using hey-api fetch-client?

from openapi-ts.

Not at the moment @vinod-canihelp. We don't have a clear section on usage with Next, though I know some people asked about it!

from openapi-ts.