Very often we embed third-party component libraries in Angular projects. But no matter how cool the library is, sometimes one needs to modify library components UI while keeping the component and added styling separated, to enable easy component upgrade and solution management. Here we present a way of overriding isolated component styles, e.g making style changes without direct modification to third-party component. Moreover, we will isolate customized components by wrapping them to modules. Modularity is one of the greatest features of Angular, allowing us to keep the project maintainable, clean and extensible.
In this tutorial, we’ll learn how to work with the wp-api-angular library that allows us to interact with the WordPress API from Angular 2+ applications. This library supports all major WP resources including users, posts, comments, media, taxonomies etc. It’s also quite simple to use, so we’ll get the idea in no time.
Last week, Ben discovered that you could listen for IMG error events using event delegation (so to speak) if we attach the event-handler to the Capture phase of the event life-cycle. As someone who works on a SaaS (Software as a Service) product that is based heavily on client-side image rendering, he's enamored with the idea of being able to track whether or not images load for their users. But, such information is only helpful if it can be reported and aggregated for consumption by his engineers. Having worked heavily with StatsD and DogStatsD on the server-side, he wondered what it would look like to report StatsD metrics directly from the browser in an Angular 5.2.9 application.