Once we implemented useQuery it replaces useState in some cases.
It's a must have for lists of an indefinite / constantly growing size. If you only have a finite number of states stored in a list then you can still use useState and keep track of your states / ids manually.
useState hasn't been optimized for large datasets. useQuery is generally preferable if you plan to increase the number of states stored in a list constantly over time.
See also #26
This involves
- Writing a medium post
- Adding detailed documentation
- Asking stackoverflow questions
All this can be done by anyone who sufficiently understands react server and the two different approaches of storing and querying data.
Once we implemented
useQueryit replacesuseStatein some cases.It's a must have for lists of an indefinite / constantly growing size. If you only have a finite number of states stored in a list then you can still use
useStateand keep track of your states / ids manually.useStatehasn't been optimized for large datasets.useQueryis generally preferable if you plan to increase the number of states stored in a list constantly over time.See also #26
This involves
All this can be done by anyone who sufficiently understands react server and the two different approaches of storing and querying data.