Eduardo San Martin Morote

## Summary There is no silver bullet to data fetching because of the different data fetching strategies and how they can define the architecture of the application and its UX....

add `useQueryState()`

3

Allows retrieving the query state by key - Should allow passing multiple keys to to match multiple queries and return the aggregated state of these queries - How should they...

- Find real-case scenarios where this is used to evaluate how important this feature is - Ideally should be tree shakable (a plugin)

A way to avoid using outside state

3

maybe a `defineQuery(() => {})` to allow using globals and creating global state associated with the query (e.g. a page?). Currently one can try to do this: ```vue const page...

Add a mutation plugin that allows setting up global options (onSuccess, etc that run after local ones)

Create a mutation store to hold the share state of mutation

Refactor types to use a union for better type narrowing

1

TS now supports type narrowing when destructuring. So it's worth having multiple types for the return values of useQuery and useMutation ```ts import { Ref, ShallowRef, ref, shallowRef } from...

- [x] Allow passing new options + types - [ ] hook into `setup()` - [ ] Move features to plugins - [ ] refetch on mount? - [ ]...

- test signals aborts if refetch is called

Preload queries

3

Allowing a query to be preloaded Requires all the options rather than just the key as otherwise it might not exist