In this post I will talk about error handling in complex RxJs streams.
The easiest way to trap errors in RxJs is to add an error callback in the subscribe call.
While this is super simple, this approach has a few shortcomings. The main issue is that if you let an error propagate up to the “catch all” handler, the underlying observable is terminated in the process.
Source: Error Handling in RxJs
Welcome back to series of blog posts about architectural patterns for frontent web applications. The code examples are written in Angular 4 but the logic is applicable in plain javascript or any modern javascript framework.
Source: Angular architecture patterns — Detailed project architecture
It struck me how painful experience it was to test an Angular app. And then I realized it can be painless with Jest.
WebStorm is a great tool for building Angular applications. One of its useful features is running tests right in the IDE. In this blog post I’ll show you how to do it.
I’ve worked with Angular.js for a few years and despite the widespread criticism I think this is a fantastic framework. I’ve started with a great book Building your own Angular.js and read most of the framework’s source code. So I want to believe I have a solid knowledge of the Angular.js inner workings and a good grasp of the ideas used to built the framework. Now, I’m trying to get to the same level of understanding with the newer Angular and map the ideas between the versions. What I’ve found is that contrary to what is usually claimed on the internet Angular borrows many ideas from its predecessor.
Source: Angular’s $digest is reborn in the newer version of Angular
Angular has many features that allow us to configure apps to be as fast and high preforming as possible. One of the critical features that enable responsive fast Angular apps is the ability to lazy load code with the Angular Router. This allows our initial bundles to remain small ensuring faster downloads and start up times for our app.
The Angular router has the amazing ability to load code on demand as the user routes between views on our apps. By splitting our features into stand alone Angular Modules we can lazy load the module when the user clicks the link to navigate to this feature.
Source: Custom Preloading and Lazy Loading Strategies with Angular
Since angular 2 brought Rxjs as embedded library, it automatically moved Rxjs to mainstream. However Rxjs is fantastic and very powerful library, there is a trade-of related to that. Rxjs is not super new concept. I have seen it couple of years ago in C# community. It raised up, as some hyped library for data flows and then moved into shadow. I was reading about that and listen a lot conferences, because a lot of people were talking about that, at these times. Eventually I never really used it in real scenario. It was one of these libraries to show on presentation, to make wow effect. It shines when you are developing some ETL or building up “typeahead” like control. However it’s really hard to find some reasonable usage of that library. You need to be familiar with some functional language, unidirectional data-flow and reactive programming concepts to use it properly for your architecture.
Source: Rxjs — be careful with that axe, Eugene – Michal Majewski – Medium
Many organizations have large AngularJS 1.x applications deployed to production. These applications may be built by multiple teams from different lines of business. They may use different routers and state management strategies. Rewriting such applications all at once, or big bang migrations, is not just impractical, it is often impossible, and mainly for business reasons. We need to do gradually, and this is what this series of articles is about.
Source: Upgrading Angular Applications: Upgrade Shell – nrwl
This post assumes that you at least have some working knowledge of Angular and Decorators.
If you have no prior knowledge on the subject, you can read the following articles:
Source: Inspiration for Custom Decorators in Angular – NetanelBasal