Now that we learned how data was shared among classes before services and that this wasn’t very DRY or scalable, let’s learn how to use services for dependency injection.
Best practices teach us the DRY principle: Don’t repeat yourself. Let’s get a real-world understanding of why this principle matters by looking at how we built components and classes before services.
Angular offers a set of pipe options to transform the way your data is displayed, allowing you to control just how it looks. Let’s examine some of these options.