-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Non-breaking React layer rewrite work #8419
Comments
from apollographql/apollo-feature-requests#366
Would this include suspense support? If so, would the goal for these changes be sometime around React 18's (unannounced) release date? Sorry to keep inquiring about this, but the (now deprecated) fork adding suspense is what keeps us on AC2 and we really don't have to revert our async handling updates. Thanks! |
We've just migrated one of our projects to React 18, and I've been working on adding Suspense support. Here is my working PoC: It looks like this: const resource = useQueryResource(query, { variables });
resource.read(); // <-- suspends The conclusion: Suspense and Apollo actually work great together (but only on |
We're polishing up our React 18 support. We're aiming to have a new |
@hwillson That's great to hear! To reiterate @rajington's question:
Does "our React 18 support" mean "basic compatibility with React 18" (i.e. one can update to React 18 and things won't immediately break) or "1st class support for Suspense as described in React 18's release announcement":
I understand if the answer is no, but across this issue and apollographql/apollo-feature-requests#366, folks are eager to get clarity from y'all on this! |
React 18 support is now available in |
We're going to publish the non-breaking React layer rewrite work as part of Apollo Client 3.6, so this issue will be used to track the non-breaking parts of apollographql/apollo-feature-requests#366. This will mostly cover:
renderHook
)The text was updated successfully, but these errors were encountered: