Hi Jo, I appreciate your time in reading and commenting!
Regarding your question about side effects and how components can be aware of updates happening in other areas of the app: You're right that httpClient returns an observable, and we can subscribe to it for responses. But the challenge is in knowing when a different part of the app has been updated.
This is where a topic or event-based service really shines. The idea is to create a central hub in your application for different events or actions. For instance, you might have subjects for updates to user profiles or changes in orders.
Whenever there's an important action, like a successful HTTP request that updates part of the app's state, you emit an event on the corresponding subject in this topic service. This way, different parts of your application can stay informed about what's happening elsewhere.
Here's how it can work in practice:
- Components interested in certain updates should subscribe to the relevant subjects in this topic service. When an event is emitted, these components get notified and can react accordingly.
- Additionally, components might also need to subscribe directly to services for the most recent state updates, particularly for responses from backend interactions.
By using this topic service for communication across components, you can manage your application's state more centrally and efficiently. It's a neat way to keep various parts of your app in sync without them directly depending on each other.
It's not a bad idea to update the article with that approach. Let me know if you think it would be helpful