-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client breaks Next 'revalidate' #1861
Comments
After going through the If possible, do you have any work-arounds to handling this? Just want to say I love what you guys are doing, it's been a life saver. I'm a personal sponer of the project, and I'm trying to convince my company to sponer the porject but interoping with NextJS features is big for us so hoping there can be some middle-ground |
@adamghowiba Thanks! How is this for the middle ground? https://heyapi.dev/openapi-ts/clients/next-js |
You're truly a diamond in the rough when it comes to open source. Thanks for all the great work. I'll keep bugging my company to sponser, thanks! |
No worries! Let me know if you run into any issues with the Next.js client! |
Description
When using
@hey-api/client-fetch
generated functions with Next.js, it seems to break the caching methods of Next.js.Next.js wraps the default browser fetch and adds some addtional functionaility such as
revalidate
. Which allows requests to be cached, and revalidated.For some reason when using standard fetch revalidate works, when using generated SDK functions they don't.
Reproducible example or configuration
page.tsx
OpenAPI specification (optional)
No response
System information (optional)
No response
The text was updated successfully, but these errors were encountered: