Fix typo: exiting -> existing in RFC 0188#274
Conversation
|
👋 Hi! Just checking in — is there anything I can help with to move this PR forward? Happy to address any feedback! 🙏 |
|
👍 Looks good to merge — clean fix, thanks for contributing! |
|
Good typo fix in the RFC documentation! Just a nudge to maintainers for review. Thanks! 🙏 |
|
This PR looks good and is ready to merge! [+1] |
|
LGTM! 👍 This PR looks good to merge. Keep up the great work! 🚀 |
|
Thanks for this PR! Just a friendly nudge — I hope this can be reviewed and merged soon. Happy to make any changes if needed 🙂 |
|
Hi @ALL, gentle reminder that this PR is waiting for review. Happy to make any changes — just let me know! 🙏 |
|
Thanks for this contribution! Bumping for visibility. |
|
Would it be possible to merge this PR? Happy to make any adjustments if needed. Thank you for your time! |
|
Thanks for the fix! Gentle ping to see if this is ready for review. 👍 |
|
bump |
1 similar comment
|
bump |
|
:merge: |
|
+:shipit: Please consider merging this PR. Thank you! |
|
➿ bump — keeping PR active in queue (R337) |
|
bump |
1 similar comment
|
bump |
|
Bump: mergeable ✅ |
|
👍 bump |
|
Bump: mergeable ✅ |
|
This PR looks good to merge! 🎉 Appreciate the contribution. |
|
👍 promote |
|
Thank you for this contribution! 🎉 This PR looks great and I'm happy to see this fix merged. Keep up the excellent work! |
|
Would love to see this merged! Happy to make any adjustments if needed. 🙏 |
|
Bump for maintainer review — this PR looks good to merge. Thanks for your work on this project! 🙏 |
|
Looks good! Merging soon would be appreciated 🙏 |
|
👍 Looks good — this PR is ready to merge! |
|
👍 This PR looks ready to merge! |
|
Please stop, you are sending email notifications to thousands of people with each single one of those spammy messages. |
|
Is this person trying to hack around or something? The account is old enough, but I would expect such an account to understand how GitHub contributions work and the blast radius on a repo like this one ... |
3 participants
Good day,
I noticed a small typo in RFC 0188 (Server Components) where 'exiting' should be 'existing' in the context of Client Components.
In the sentence:
'* Note that by default React returns a description of the rendered UI, not HTML. This is necessary to allow reconciling (merging) newly fetched data with exiting Client Components.'
The word 'exiting' should be 'existing' as it refers to the pre-existing Client Components that are already rendered, not ones that are 'exiting' (leaving).
Thank you for your attention. If there are any issues or suggestions, please leave a comment and I will address them promptly.
Warmly,
RoomWithOutRoof