Move name for React quote in FRAMEWORKS.md

nicolo-ribaudo · web-flow · commit 974ebe7c1b2d · 2025-03-26T14:08:15.000+01:00
diff --git 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.
+> — <cite>Joseph Savona, React team</cite>
 
 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.
->
-> — <cite>Joseph Savona, React team</cite>
 
 ## [Solid](https://www.solidjs.com/)
 

Original file line number	Diff line number	Diff line change
`@@ -49,6 +49,7 @@ Note: [client] and [server] markers in messages have been added by the p`
`49`	`49`	`> 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.`
`50`	`50`	`>`
`51`	`51`	`> 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.`
	`52`	`+> — <cite>Joseph Savona, React team</cite>`
`52`	`53`
`53`	`54`	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.
`54`	`55`
`@@ -78,8 +79,6 @@ The following is a quote [from the React docs](https://react.dev/reference/react`
`78`	`79`	> ```
`79`	`80`	`>`
`80`	`81`	`> 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.`
`81`		`->`
`82`		`-> — <cite>Joseph Savona, React team</cite>`
`83`	`82`
`84`	`83`	`## [Solid](https://www.solidjs.com/)`
`85`	`84`