Closed johnclary closed 12 months ago
Started looking into this some yesterday (9/11/23), but I'm going to put it on hold until syncing with John and Chia on other work related to the project list view
Some links:
connectToDevTools = true
in the client instance passed to ApolloProvider
in App.js
to get the tools to work) https://www.apollographql.com/docs/react/development-testing/developer-tooling/#configurationGoing to keep this one's status as-is for now. Met with John and Chia yesterday, and we identified short term fixes like lowering the default number of rows and longer term fixes like exploring alternatives to gql abstract. Caching could help us after looking at those solutions.
Thanks, Mike—I have marked it as blocked by https://github.com/cityofaustin/atd-data-tech/issues/13844. Moving to backlog.
@mddilley those resources were super helpful! thanks for your research on this!
When navigating back and forth between the project list and project details, it becomes apparent that the data that powers the project list is not cached.
The desired behavior is that previously queried data is always cached so that the project list is not blocked from rendering. The app should also refetch for updated data in the background.