Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Deprecate next field in Fetch client #1862

Closed
mrlubos opened this issue Mar 26, 2025 · 0 comments · Fixed by #1899
Closed

Deprecate next field in Fetch client #1862

mrlubos opened this issue Mar 26, 2025 · 0 comments · Fixed by #1899
Labels
docs 📃 Improvements or additions to documentation feature 🚀 New feature or request

Comments

@mrlubos
Copy link
Member

mrlubos commented Mar 26, 2025

Deprecate the field and set it to never to point people to migrate to the Next.js client so they don't have to guess why Next-specific features don't work.
@mrlubos mrlubos added docs 📃 Improvements or additions to documentation feature 🚀 New feature or request labels Mar 26, 2025
@mrlubos mrlubos mentioned this issue Apr 2, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs 📃 Improvements or additions to documentation feature 🚀 New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: set next field to never and recommend next.js client hey-api/openapi-ts
1 participant
@mrlubos