From 974ebe7c1b2d66ff477dd2b4088b51c3a063b19a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=B2=20Ribaudo?= Date: Wed, 26 Mar 2025 14:08:15 +0100 Subject: [PATCH 1/2] Move name for React quote in FRAMEWORKS.md --- FRAMEWORKS.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/FRAMEWORKS.md b/FRAMEWORKS.md index d46ec05..fa22e5f 100644 --- a/FRAMEWORKS.md +++ b/FRAMEWORKS.md @@ -49,6 +49,7 @@ Note: **[client]** and **[server]** markers in messages have been added by the p > 2. Attempt to compile _all_ async/await code that might appear in a React application to automatically pass through the context. Compiling React code for React is one thing, compiling all user code for React is invasive and a non-starter. > > That leaves us with needing some built-in way to associate a context across async yield points. Crucially, this is not just a framework concern but something that impacts how users write asynchronous code, since the workarounds are for them to write code differently. We understand that the specific solution here may have performance and/or complexity concerns and are happy to collaborate on alternative implementations if they can provide a similar capability. +> — Joseph Savona, React team The following is a quote [from the React docs](https://react.dev/reference/react/useTransition#troubleshooting) showing a developer error that is common enough to be included in their documentation, and that would be solved by browsers providing `AsyncContext` support. @@ -78,8 +79,6 @@ The following is a quote [from the React docs](https://react.dev/reference/react > ``` > > This is a JavaScript limitation due to React losing the scope of the async context. In the future, when AsyncContext is available, this limitation will be removed. -> -> — Joseph Savona, React team ## [Solid](https://www.solidjs.com/) From 06e96a9133f693acc8c8118b189315e406291113 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=B2=20Ribaudo?= Date: Wed, 26 Mar 2025 14:08:46 +0100 Subject: [PATCH 2/2] Update FRAMEWORKS.md --- FRAMEWORKS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/FRAMEWORKS.md b/FRAMEWORKS.md index fa22e5f..862550f 100644 --- a/FRAMEWORKS.md +++ b/FRAMEWORKS.md @@ -49,6 +49,7 @@ Note: **[client]** and **[server]** markers in messages have been added by the p > 2. Attempt to compile _all_ async/await code that might appear in a React application to automatically pass through the context. Compiling React code for React is one thing, compiling all user code for React is invasive and a non-starter. > > That leaves us with needing some built-in way to associate a context across async yield points. Crucially, this is not just a framework concern but something that impacts how users write asynchronous code, since the workarounds are for them to write code differently. We understand that the specific solution here may have performance and/or complexity concerns and are happy to collaborate on alternative implementations if they can provide a similar capability. +> > — Joseph Savona, React team The following is a quote [from the React docs](https://react.dev/reference/react/useTransition#troubleshooting) showing a developer error that is common enough to be included in their documentation, and that would be solved by browsers providing `AsyncContext` support.