Congratulations! We've successfully updated our code to establish a reactive data flow within our application using the in-memory web API and the Angular HTTP client. We are using RxJS observables, transforming them using operators, and resolving our data directly within the view using the Angular async pipe. This refactoring was quite a technical but significant change. We're now following a very clean approach on how to react to application state changes. Our observable streams are router down directly into the view where we then subscribe using the async pipe. If Angular destroys our task list component, the async pipe will also take care of the necessary unsubscriptions. We've learned about the following topics:
- The Angular in-memory ...
