Does the module returned by the static forRoot method come with the providers declared in @NgModule() decorator? I thought that is an interesting question because Angular can act either way. The method forRoot returns an object that implements ModuleWithProviders which consists of a reference to an Angular ngModule and a list of providers
Like most of you, I work in a team of a couple of programmers and our responsibility is to handle a few big Angular projects. In order to keep our project's codebase clean, readable and without any bugs we try to use verified Angular patterns. One of them is obviously the Smart and dumb components pattern
Recently I had the pleasure of doing a small refactor in an Angular project. Refactor is one of my favorite things to do so I was glad that I had a chance to do it. It wasn't anything especially complicated, a basic name change, but the interesting part is that after my modifications our unit tests started to fail. I was confused by the whole situation so I started to unravel the mystery that was behind the failing tests
The RxJs library is a great set of tools that can help you bring your application reactivity to the next level. One of the various features of Observables is that they return a series of values. You can simply connect to a stream of data and receive various values over a period of time
Every good programmer should know this famous Robert C. Martin concept "Good architecture allows us to delay making serious decisions as long as possible". This quote should be taken into consideration every time an architectural decision is being made. It is especially important in today's frontend development where everything is rapidly changing.
The smart and dumb components pattern is a very commonly used practice. I like to call it pure and impure, I feel that it makes more sense when you take functional programming into consideration. There are also other names for this pattern: "Container and Presentational", "Advanced and Simple".