Suspense Stability
How rigid should I be about versions with react-query and Suspense? For example, if I am on a floating react-query@v4 and floating react@18, is it likely that the Suspense-enabled fetching API will break within the same major version?
6 Replies
ambitious-aqua•3y ago
use v5 for suspense please
modern-tealOP•3y ago
Ok. So if I’m on floating v5 and floating React 18 (like let’s say I’m using an unpkg UMD with @18, so I get the latest minor and patch version), am I at risk of the Suspense-enabled fetch API changing and breaking me?
ambitious-aqua•3y ago
no, suspense is no longer experimental so we'll adhere to semver
there's one open bug that will change behaviour when fixed
modern-tealOP•3y ago
Cool. Thanks!
stormy-gold•3y ago
edit: nvm i just noticed the docs describing that you can't conditionally enable/disable requests (although the type definitions still show 'enabled')
Hi there, is there any known issue on react-query:5.8.4 with useSuspenseQuery not respecting the 'enabled' property?
I'm noticing that useSuspenseQuery does not respect the 'enabled' flag, but if i switch the function to useQuery then 'enabled' is respected
ambitious-aqua•3y ago
It shouldn't be there on type level either