Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
global mutate can't revalidate useSWRInfinite data
See original GitHub issueBug report
Description / Observed Behavior
What kind of issues did you encounter with SWR?
For example a Todo app, on the list page:
I using useSWRInfinite to load todos, the first page’s key is /api/todos,
Then I delete a Todo (send request to backend to deleted it), and I need revalidate the data:
If I use mutate returned from the useSWRInfinite call, it will work.
If I use mutate from const { mutate } = useSWRConfig(), it will not work.
Expected Behavior
How did you expect SWR to behave here?
Both way need way. because I may call the delete not on the same component, so I can’t pass the mutate function to other component
Repro Steps / Code Example
Additional Context
SWR version. 1.0.1
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We should add this to the docs, but there is currently a bug in Nextra blocking this…
@ezeikel Good point! I opened https://github.com/vercel/swr-site/issues/264 for this doc requirement