gabotorresruiz commented on issue #39209: URL: https://github.com/apache/superset/issues/39209#issuecomment-4422760537
> Tanstack 5 introduces [support for suspense](https://tanstack.com/query/v5/docs/framework/react/guides/suspense)---do we plan to go that route or would we stick with the imperative strategy we use currently? @mikebridge We'd start with the imperative pattern (`useQuery` / `useMutation`) for the migration since it's a 1:1 replacement for the current `useState + useEffect + SupersetClient` pattern. `Suspense` adoption comes as a follow-on once `Suspense` and `Error boundaries` are added at the page level, which is a separate effort. The migration makes `Suspense` possible, but doesn't require it. Both patterns share the same `QueryClient cache`, so teams can adopt `Suspense` incrementally per page or section as the boundaries get added. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
