Shu Ding

Yep @gaearon @devknoll this is what we are going to do, there is also #1832 and #1841. Our plan is to: - 1.x which is the current version: show a...

> most suspense-like libraries probably don't properly support SSR I see this as a general problem of “Suspense for data fetching in SSR” though. But still, if the data is...

Hey @pkellner! From the SWR side there isn't much I can do – in #1931 we already made SWR behaving correctly with Suspense and SSR. I guess the next step...

Thanks for reporting this! If we make the `mutate` function a snapshotted value, there are also many downsides: ```js const { mutate } = useSWR(...) useEffect(() => { // do...

No it’s not added yet. I don’t think this can be handled by TypeScript because configs can be inherited from `SWRConfig`. What we can do temporarily is to support the...

By definition, `useSWRSuspense` should override the global config of `suspense: false`. Also, it would be great to cover more use cases such as waterfall (#5, #168) and dependents with this...

We can just add this, but I'd love to hear more feedback about **why** there's a need to clear the cache (and why it can't be done via changing the...

Totally agreed. It is also my biggest concern that we are not reusing the implementation of SWR's core. We should evaluate the difficulty of making the core support a list...

Thanks for reporting! We haven’t got similar reports about this yet, will keep this open for now.

Thanks for reporting this! First of all the intention wasn’t to make this breaking. If the behavior changes that should be fixed. We will also update the docs, great catch...