If you use Angular Material, and you have been looking for a way to launch the dialog component via the url, this is the article for you. Two different options are proposed, both with pros and cons depending on whether or not you are managing state globally with a solution like NgRx.
But as users of the web, we expect to be able to navigate to an experience by following a link (in the above example, clicking “Open Dialog” anchor) or by entering the URL directly. How can we provide the latter using Material Dialogs?
Sometimes to understand where you're going, you have to look at where you've been. This walk down memory lane through the history of AngularJS and Angular helps paint the picture of the future of Angular. With the Ivy compiler's pending release in Angular 8, the future certainly seems bright!
None of these frameworks rocketed to popularity. The world was waiting for something better. In 2010, that something better appeared — it was named Angular.
This article does a great job explaining how you can use three different observable operators to dynamically filter a result set in a form input. Alain does a great job clearly explaining not only how the operators work but why you should use them.
In this tutorial, we saw how to combine three different operators (combineLatest, map, and startWith) in order to achieve reactive filtering on a dataset using user input as a filtering criterion.
Netanel has done it again. This time, showing how to create a custom file upload component using the custom value accessor. Great code examples as always. If you have 5 minutes to spare, you should check this out.
In this article, I’ll walk you through the process of creating a reactive form that includes a file upload, along with the normal form fields. Along the way, we’ll create a custom form control for our file input, add validation and create custom RxJS operators.
This article, while brief, digs deep into how to create a plugin based architecture for your Angular applications. You'll better understand how your applications are bootstrapped and how your lazy loaded modules will communicate at runtime.
I would like to share my thoughts how to build a pluggable Angular Frontend with modules which you can combine together like a puzzle. Modules should not know each other — that means, they don’t have cross-dependencies. Modules should be lazy loaded at runtime by means of backend configuration which specifies what modules your UI has exactly. In other words, the functionality scope depends on the logged in user, more exactly on the user role, such as “customer”, “developer”, etc.
This is a great walkthrough of error handling in RxJS in general and especially with NgRx effects.
When you use the catchError operator you are adding error handling to the observable itself. When an error occurs catchError will allow you to create a value to return to the stream that covers when an error occurs. Using throwError here creates an observable that is returned from this call that replaces the value that would have been returned on success.