Skip to content

suspense documentation may need updating #2028

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
laurencefass opened this issue Jun 13, 2022 · 2 comments
Closed

suspense documentation may need updating #2028

laurencefass opened this issue Jun 13, 2022 · 2 comments

Comments

@laurencefass
Copy link

laurencefass commented Jun 13, 2022

Bug report

This isnt a software bug, more of a document error/query, but you dont have a issue classification for that.

Description / Observed Behavior

https://swr.vercel.app/docs/suspense says:

Suspense is currently an experimental feature of React. These APIs may change significantly and without a warning before they become a part of React.... Note that React Suspense is not yet supported in SSR mode.

I think Suspense SSR is now a feature....

reactwg/react-18#37

Is this documentation still relevant/up-to-date?

Thanks

What kind of issues did you encounter with SWR?

Expected Behavior

How did you expect SWR to behave here?

Repro Steps / Code Example

Or share your code snippet or a CodeSandbox link is also appreciated!

Additional Context

SWR version.
Add any other context about the problem here.

@laurencefass laurencefass changed the title documentation outdated. suspense documentation may need updating Jun 13, 2022
@guilherssousa
Copy link

You could open the issue or even a PR correcting the observed notes on the official docs repo vercel/swr-site.

@shuding
Copy link
Member

shuding commented Jul 4, 2022

Suspense is still not recommended for data-fetching libraries, please see #1906 for more details.

@shuding shuding closed this as completed Jul 4, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants