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

useFetch is not preserving state when key or url is same #15600

Closed
examgoal opened this issue Dec 22, 2022 · 3 comments
Closed

useFetch is not preserving state when key or url is same #15600

examgoal opened this issue Dec 22, 2022 · 3 comments
Labels
3.x pending triage

Comments

@examgoal
Copy link

Environment

  • Operating System: Darwin
  • Node Version: v18.11.0
  • Nuxt Version: 3.0.0
  • Nitro Version: 0.5.4
  • Package Manager: npm@8.19.2
  • Builder: vite
  • User Config: -
  • Runtime Modules: -
  • Build Modules: -

Reproduction

Visit this URL for reproduction: https://stackblitz.com/edit/github-dgdjfn

Describe the bug

useFetch is not preserving state if the URL or the options key is the same

Additional context

No response

Logs

No response
@examgoal
Copy link
Author

any update?

@examgoal
Copy link
Author

examgoal commented Jan 3, 2023

anyone any update?

@danielroe Volta.net
Copy link
Member

Yes, we deliberately no longer cache useFetch and useAsyncData: nuxt/framework#8885

@danielroe danielroe closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2023
@danielroe danielroe added the 3.x label Jan 19, 2023
@danielroe danielroe transferred this issue from nuxt/framework Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.x pending triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danielroe @examgoal