Sam Julien not only spoke at ng-conf 2019, but he also put together a very comprehensive and well organized summary of the state of Angular as presented at the conference. Included are links to the conference videos and a github repository of the speaker's slide decks. This content is relevant whether or not you were able to attend or watch the livestream of ng-conf.
Have you ever had to set up a proxy for your development environment? This powerful technique is especially useful if you have an Angular application that interacts with multiple API's. This short article explains a couple ways to configure your development environment to utilize the built in proxy capabilities of the Angular CLI.
Careful planning at the beginning of development can pay dividends when your application begins to get large. Especially something as simple as your application and file organization. You'll read about the four common types of modules used in Angular applications and how you can structure your code to scale at the largest of enterprises.
In this article, Arjen updates the state of Angular as it relates to PWA's. SWPush has been updated to allow for interaction with push notifications as of Angular 7.1. You'll learn how subscribing to notificationClicks makes this all happen. Additionally, SWUpdate has been "updated" to provide a much more elegant way of loading newer versions of the service worker without negatively impacting your users.
You can see the code examples and explanations in this great article!
Are you looking for the latest and greatest tips for improving the performance of your Angular applications? Look no further than this talk presented by Minko at #ngconf2019!
Not only does Jennifer show how to use the Control Value Accessor in your applications, but she also goes so far as to show how to properly test the code examples that she creates during the talk!
If you've been considering introducint NgRx into your application, be sure to check out this article on the ngrx/router-store. Not only does this tell you what the router-store is, it explains how to use it and more importantly WHY you should use it in certain situations.
When relying on Angular’s routing system, we rely on data persistence through params from navigation/router state. If a child or sibling component requires that data, it becomes coupled with the parent and data needs to be presented again in order to be consumed. While factory patterns may solve this issue, it can quickly get messy if external entry is granted without explicit knowledge.
In larger teams, factory patterns may not be enough to control the flow and history of data and human error may introduce inconsistencies in the code.