react-query-questions
solid-query-questions
table-questions
virtual-questions
router-questions
react-charts-questions
ranger-questions
vue-query-questions
svelte-query-questions
bling-questions
form-questions
angular-query-questions
start-questions
db-questions
start-showcase
router-showcase
📣-announcements
Taking params via quercollection options
createOptimisticAction rollback too returning in the mutationFn does nothing
collection insert rollback instantly
Is collection schema just for type inference, or is it leveraged internally for other operations?
Best practice suggestion: Should I avoid mapping over api data?
Best practice suggestion: Should I strip pagination information?
({ total: data.total, items: data.items })
--> data.items
...is a live query collection just an alias for a regular collection?
Pattern: Populating a collection "as needed" with multiple Queries throughout app - no "base" query.
useQuery
hooks throughout the app to "feed" our collections, only adding records as they're called for throughout the app.
We don't want to force the user to load entire db tables since 95% of the time they will only use a small % of them. We do want to progressively build up a store and use it's querying methods to performantly select from the data that has been fetched.
As of 7/31 we have "manual sync update methods" per this issue: https://github.com/TanStack/db/issues/294...Syncing Paginated Rest API
Questions about Purpose
