I teamed up again with Tomek Ducin for a hands-on look at front-end state management using React Query (now Tanstack Query). We cover how separating local UI state (like toggles and forms) from server data prevents stale info, redundant fetching, and messy code. Tomek showed how React Query can encapsulates: caching, time-to-live, and refetching and other stuff you shouldn't be implementing on your own. He also showed the overlap with backend patterns like pub/sub, proving these concepts span the entire stack.
Great talks again. I used MobX to do a fraction of that before knew react query, fortunately not too much hassle probably compared to if I am using Redux.
In the end of the video, you were suggesting next topic and I am very interested in how to manage what should we store between React Query and State Manager, is some duplication is OK?
Because especially with MobX and other Signal based state manager that do fine-grained reactivity, probably some area can be better in state, or duplicated on, or passed through state before reaching the component.
Great talks again. I used MobX to do a fraction of that before knew react query, fortunately not too much hassle probably compared to if I am using Redux.
In the end of the video, you were suggesting next topic and I am very interested in how to manage what should we store between React Query and State Manager, is some duplication is OK?
Because especially with MobX and other Signal based state manager that do fine-grained reactivity, probably some area can be better in state, or duplicated on, or passed through state before reaching the component.