Best practices: components responsible for querying
Love this library and I've been using it for quite some time. I'm struggling to get folks on board w/ tanstack/query for our next phase dev. I came a across this article a while ago and I think it succinctly summarizes the opinion of the hold outs:
Any clever response to the thoughts below?
https://nikoheikkila.fi/blog/clean-frontend-architecture-with-sveltekit/discovering-the-use-cases/#user-content-fnref-2
Any clever response to the thoughts below?
https://nikoheikkila.fi/blog/clean-frontend-architecture-with-sveltekit/discovering-the-use-cases/#user-content-fnref-2
1. ....Some special utility libraries, such as React Query, endorse it as a best practice. In this fashion, components fetch data and render their HTML based on whether the internal state of a query is pending, rejected, or fulfilled. It does this so you don't have to touch the global state
2. But I'm afraid of no state, and neither should you be!I don't recommend having components responsible for querying data because their responsibility is already in presenting the data. More accurately, components need only receive data from view models, format it, and output it to the screen. Instead, I advise you to follow either of the three following ways:
Niko Heikkilä
Why designing loosely coupled applications is crucial for managing complexity and sustaining maintainability.
