-
Notifications
You must be signed in to change notification settings - Fork 407
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
Optional suspense #255
Optional suspense #255
Conversation
Thanks for the hard work, is there anything I can do to help get this across the line? |
Seems like one of the pipelines is stuck since a few months. Is this PR dead? |
i'd be very keen on using this in the current stable react version. Any idea's on when this is being merged? |
@jhuleatt @jamesdaniels Any chance this proposal may make it any time soon into ReactFire? Since it was mentioned in #260 and there's great interest in using ReactFire with the stable builds of React. Thank you for your work on this! |
Hey there, apologies for the long silence on this. We're working on reviving this PR, and I've just pushed the latest updates. Examples of the new api can be found here: https://github.com/FirebaseExtended/reactfire/tree/optional-suspense/example/withoutSuspense If you want to pull this branch yourself and try things out, pull it then run: In one terminal: yarn
yarn start In a second terminal: cd example
yarn
yarn start |
Hello folks, |
What's happening?
This is a proposed API change that makes it easier to use ReactFire without enabling experimental React features (Suspense & Concurrent Mode).
"Suspense Mode" will be settable in
FirebaseAppProvider
(in which case it will automatically apply to all children ofFirebaseAppProvider
), or in individual calls as part ofReactFireOptions
.If you don't set
suspense={true}
inFirebaseAppProvider
, it will default tofalse
.Now that Suspense won't necessarily be handling loading states, each hook will return more information about its status:
Status