Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Reactive Patterns with RxJS for Angular
  • Toc
  • feedback
Reactive Patterns with RxJS for Angular

Reactive Patterns with RxJS for Angular

By : Lamis Chebbi
4.1 (16)
close
Reactive Patterns with RxJS for Angular

Reactive Patterns with RxJS for Angular

4.1 (16)
By: Lamis Chebbi

Overview of this book

RxJS is a fast, reliable, and compact library for handling asynchronous and event-based programs. It is a first-class citizen in Angular and enables web developers to enhance application performance, code quality, and user experience, so using reactive patterns in your Angular web development projects can improve user interaction on your apps, which will significantly improve the ROI of your applications. This book is a step-by-step guide to learning everything about RxJS and reactivity. You'll begin by understanding the importance of the reactive paradigm and the new features of RxJS 7. Next, you'll discover various reactive patterns, based on real-world use cases, for managing your application’s data efficiently and implementing common features using the fewest lines of code. As you build a complete application progressively throughout the book, you'll learn how to handle your app data reactively and explore different patterns that enhance the user experience and code quality, while also improving the maintainability of Angular apps and the developer's productivity. Finally, you'll test your asynchronous streams and enhance the performance and quality of your applications by following best practices. By the end of this RxJS Angular book, you'll be able to develop Angular applications by implementing reactive patterns.
Table of Contents (19 chapters)
close
1
Part 1 – Introduction
5
Part 2 – A Trip into Reactive Patterns
10
Part 3 – Multicasting Takes You to New Places
16
Part 4 – Final Touch

Exploring the declarative pattern for filtering data

You should think of everything as a stream. This is the golden rule.

We have recipes$, which is our data stream. What if we were to consider the click on the See results button as a stream as well? We don't know when, but every time the user clicks on See results, the action stream emits the value of the filter.

In total, we have the data stream (responsible for getting the data) and the action stream (responsible for emitting the latest value of the filter). Both of the streams rely on each other; when recipes$ emits a new value, the filter should stay active, and when the filter emits a new value, the recipes list should be updated accordingly.

What we are really trying to do is get information from different streams. And whenever you want to join information from multiple observables, you should think of one of the combination operators available in RxJS.

Instead of getting the data we need from both streams...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete