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.

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

doc: Update wording for the "missing suspense boundary" guidelines #847

Open
wants to merge 1 commit into
base: next
Choose a base branch
from

Conversation

mtlaso
Copy link

@mtlaso mtlaso commented Jan 5, 2025

Updating the wording of Client components need to be wrapped in a boundary section based on the discussion at #846

Updating the wording based on the discussion at 47ng#846
Copy link

vercel bot commented Jan 5, 2025

@mtlaso is attempting to deploy a commit to the 47ng Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

vercel bot commented Jan 5, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nuqs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 5, 2025 8:01am

@franky47 franky47 added the documentation Improvements or additions to documentation label Jan 5, 2025
@franky47 franky47 added this to the 🪵 Backlog milestone Jan 5, 2025
@franky47
Copy link
Member

franky47 commented Jan 5, 2025

Thanks!

@franky47 franky47 changed the title Update troubleshooting.mdx doc: Update wording for the "missing suspense boundary" guidelines Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants