Skip to main content

Angular pure and impure pipes explained

Angular Pipes are one of the best way to format data, we will see how this is functioning internally and also We will see the following additional things,

·   What are Angular pipes,

·   What are pure and impure pipes,

·   Why we need two different types of pipes

·   How to implement the two types of pipes

·   What are the advantages over one another?


Angular Pipes:

 

Imagine a simple pipe where a liquid flows into one side and flows out other side, and imagine inside the pipe something is happening and the output is different, the same mechanism is being applied to Angular Pipes, the data is flown into Angular Pipes and it does some changes / decoration / fine tuning whatever we call to change the data and emits the data outside.

 

A simple example of a pipe is uppercase pipe

From Angular official tutorial page, we can see a simple example for a pipe to convert the data to upper case

A pipe will have the following,

·   Inside the interpolation, that is double parenthesis {{ }}, there should be a value expression

·   after that we need a pipe symbol to mention we are going to use some pipe | and then the pipe name, in this example the uppercase is the pipe name

So, the input will be translated into uppercase as output here

 

What is the Difference between pure pipes and impure pipes in Angular?

Pure Pipes:

Only called when the values changes associated with it

Implementation:

By default the pipes are pure by nature,

 

 Impure Pipes:

 Called every time any other value changes 

 Implementation: 

We need to set pure as false in order to initiate this. 


(To be continued!)


The complete code is available in the following GitHub Repo: https://github.com/oneananda/angular-pure-impure-pipes

This is explained in the following YouTube videos.

https://www.youtube.com/watch?v=eKqqYBF6Igw

https://www.youtube.com/shorts/7VG_DJJmZwg



Labels:

Comments

Post a Comment

Popular posts from this blog

Using of global variables in C# - Drawbacks & Solutions

How using global variables can have implications on the design, maintainability, and test-ability of C# code: Harder to understand and reason about the code:       class Program     {         public static int globalCounter = 0;         static void Main()         {             globalCounter++;             Console.WriteLine(globalCounter);         }     }   In this example, the global variable globalCounter is accessible from anywhere in the program, including the Main method. It's not clear where the value of the globalCounter is updated, it could be updated in other methods or classes, making it harder to trace the flow of data and understand the source of bugs.   More prone to errors:       class Program     {         public static string globalString;         static void Main()         {             globalString = "Hello" ;             Method1();             Method2();         }         static void Method1()         {
Post a Comment
Read more

Task Parallel Library (TPL) and Akka.NET Alternatives

Task Parallel Library (TPL) and Akka.NET are among the most commonly used libraries for parallel and concurrent programming in the .NET ecosystem. However, there are also several other options available, depending on your specific needs: Parallel Language Integrated Query (PLINQ) is a parallel programming feature of .NET that provides an easy and efficient way to perform operations on collections in parallel. LINQ (Language Integrated Query) is a powerful feature in .NET that allows developers to work with data in a more declarative and language-integrated manner. While LINQ queries are inherently sequential, PLINQ extends LINQ by providing parallel versions of the query operators, allowing some queries to execute faster by utilizing multiple processors or cores on a machine. PLINQ is great when you are working with large collections where operations might be CPU-intensive or I/O-bound and could potentially be sped up by parallel execution. Here is a simple example of a PLI
Post a Comment
Read more

SOLID Principles with Real World examples in C#

  SOLID Principles with Real World examples in C#   SOLID principles are formed by using S Single Responsibility Principles (SRP) O Open Closed Principle (OCP) L Liskov’s Substitution Principle (LCP) I Interface Segregation Principle (ISP) D Dependency Inversion Principle (DIP)   S Single Responsibility Principles (SRP) There should never be more than one reason for a class to change, to be precise one class should have only one responsibility Single Responsibility Principles (SRP) Real world example, A perfect match for SRP is Microservices , a Microservice will not contain functionalities other than the one it is designated to do,  Example ·                   Order Processing Service, ·                   Shipment Management Service, ·                   User Authentication Service, ·                   Catalogue List Service       class OrderProcessor     {         public void Process(Order order)         {             // Check inven
Post a Comment
Read more