Merge branch 'main' into add-challenge-simple-animations

docs/src/content/authors/wandrille-guesdon.json

@@ -0,0 +1,5 @@
+{
+  "name": "Wandrille Guesdon",
+  "linkedin": "https://www.linkedin.com/in/wandrille-guesdon-53a54684/",
+  "github": "https://github.com/wandri"
+}

docs/src/content/docs/challenges/angular/1-projection.md

@@ -40,4 +40,4 @@ While the application works, the developer experience is far from being optimal.
 
 - Try to work with the new built-in control flow syntax for loops and conditionals (documentation [here](https://angular.dev/guide/templates/control-flow))
 - Use the signal API to manage your components state (documentation [here](https://angular.dev/guide/signals))
-- To reference the template, use a directive instead of magic strings
+- To reference the template, use a directive instead of magic strings ([What is wrong with magic strings?](https://softwareengineering.stackexchange.com/a/365344))

docs/src/content/docs/challenges/angular/10-pipe-utility.md

@@ -8,14 +8,27 @@ sidebar:
   order: 202
 ---
 
-The goal of this series of 3 pipe challenges is to master **pipe** in Angular.
+## Information
 
-Pure pipes are a very useful way to transform data from your template. The difference between calling a function and a pipe is that pure pipes are memoized. So they won't be recalculated every change detection cycle if their inputs haven't changed.
+This is the third of three `@Pipe()` challenges, the goal of this series is to master **pipes** in Angular.
 
-## Information:
+Pipes are a very powerful way to transform data in your template. The difference between calling a function and a pipe is that pure pipes are memoized. So they won't be recalculated every change detection cycle if their inputs haven't changed.
 
-In this third exercice, you want to access utils functions. Currently you cannot access them directly from your template. The goal is to create a specific pipe for this utils file where you will need to pass the name of the function you want to call and the needed arguments.
+Pipes are designed to be efficient and optimized for performance. They use change detection mechanisms to only recalculate the value if the input changes, to minimize unnecessary calculations and improving rendering performance.
 
-## Constraints:
+By default a pipe is pure, you should be aware that setting `pure` to false is prone to be inefficient, because it increases the amount of rerenders.
 
-- must be strongly typed
+:::note
+A **pure** pipe is only called when the value changes.\
+A **impure** pipe is called every change detection cycle.
+:::
+
+There are some useful predefined pipes like the DatePipe, UpperCasePipe and CurrencyPipe. To learn more about pipes in Angular, check the API documentation [here](https://angular.io/guide/pipes).
+
+## Statement
+
+In this exercise, you want to access utils functions. Currently you cannot access them directly from your template. The goal is to create a specific pipe for this utils file, where you will need to pass the name of the function you want to call and the needed arguments.
+
+## Constraints
+
+- Must be strongly typed

docs/src/content/docs/challenges/angular/22-router-input.md

@@ -23,4 +23,4 @@ In version 16, Angular introduced a new `Input` that can listen to route data. Y
 
 ## Statement
 
-The goal of this exercice is to refactor the code to use the new `RouterInput` strategy.
+The goal of this exercise is to refactor the code to use the new `RouterInput` strategy.

docs/src/content/docs/challenges/angular/3-directive-enhancement.md

@@ -10,20 +10,20 @@ sidebar:
 ---
 
 :::note
-This exercice can feel obsolete with the new control flow and the empty block inside the `@for` block. However **structural directives** are not going to be deleted any time soon, so you can still learn a lot from this exercice.
+This exercise can feel obsolete with the new control flow and the empty block inside the `@for` block. However **structural directives** are not going to be deleted any time soon, so you can still learn a lot from this exercise.
 :::
 
 ## Information
 
-Directive is a very powerful tool only offered by the Angular framework. You can apply the DRY principal by having shared logic inside a directive and applying it to any component you want.
+Directive is a very powerful tool only offered by the Angular framework. You can apply the DRY principle by having shared logic inside a directive and applying it to any component you want.
 
 But the real power is that you can enhance an already existing directive which moreover doesn't **belong** to you.
 
 ## Statement
 
-In this exercice, we have a want to display a list of persons. If the list is empty, you must display _" the list is empty !! "_.
+In this exercise, we have a want to display a list of persons. If the list is empty, you must display _" the list is empty !! "_.
 
-Currently we have :
+Currently we have:
 
 ```typescript
     <ng-container *ngIf="persons.length > 0; else emptyList">
@@ -34,7 +34,7 @@ Currently we have :
     <ng-template #emptyList>The list is empty !!</ng-template>
 ```
 
-We want to get rid of the ng-container by writing :
+We want to get rid of the `ng-container` by writing:
 
 ```typescript
     <div *ngFor="let person of persons; empty: emptyList">
@@ -43,4 +43,4 @@ We want to get rid of the ng-container by writing :
     <ng-template #emptyList>The list is empty !!</ng-template>
 ```
 
-The goal is to **improve the ngFor directive**
+The goal is to **improve the ngFor directive**.

docs/src/content/docs/challenges/angular/4-context-outlet-typed.md

@@ -17,9 +17,9 @@ However the context of **NgTemplateOutlet** type is **Object**. But with the hel
 
 ## Statement
 
-In this exercice, we want to learn how to strongly type our ng-template in our AppComponent.
+In this exercise, we want to learn how to strongly type our ng-template in our AppComponent.
 
-This exercice has two levels of complexity.
+This exercise has two levels of complexity.
 
 ### Level 1: known Interface
 

docs/src/content/docs/challenges/angular/45-react-in-angular.md

@@ -0,0 +1,77 @@
+---
+title: 🔴 React in angular
+description: Challenge 45 is about learning how to benefit from the numerous libraries in React
+author: wandrille-guesdon
+challengeNumber: 45
+command: angular-react-in-angular
+sidebar:
+  order: 209
+  badge: New
+---
+
+The goal of this challenge is to use a React component inside an Angular application.
+
+Many components are available in React, and it can be interesting to use them in an Angular application. The goal is to create a React component and use it in an Angular application.
+
+## Information
+
+In this challenge, we have a simple application and a React component `ReactPost` in `app/react` to illustrate a React component from a library.
+
+## Statement
+
+- Your task is to display the posts with the React component `ReactPost`.
+- When you select a post, the post should be highlighted.
+
+In order to play with the React component, you should start by installing the React dependencies.
+
+```bash
+npm i --save react react-dom
+npm i --save-dev @types/react @types/react-dom
+```
+
+## Constraints
+
+- Do not transform the React component into an Angular component. The React component is pretty simple and can be written with ease in Angular. But **the goal is to use the React component**.
+
+### Hint
+
+<details>
+  <summary>Hint 1 - Configuration</summary>
+  Allow the React files in tsconfig.json
+
+```
+{
+...
+"compilerOptions": {
+  ...
+  "jsx": "react"
+},
+...
+}
+```
+
+</details>
+
+<details>
+  <summary>Hint 2 - Initialization</summary>
+  Create a react root with `createRoot(...)`
+</details>
+
+<details>
+  <summary>Hint 3 - Display</summary>
+  To render the component, it should look like this:
+
+    ```
+    <react root>.render(
+        <React.StrictMode>
+        ...
+        </React.StrictMode>
+    )
+    ```
+
+</details>
+
+<details>
+  <summary>Hint 4 - Design</summary>
+  Do not forget to allow the react file in Tailwind.
+</details>

docs/src/content/docs/challenges/angular/5-crud.md

@@ -14,7 +14,7 @@ Communicating and having a global/local state in sync with your backend is the h
 
 ## Statement
 
-In this exercice, you have a small CRUD application, which get a list of TODOS, update and delete some todos.
+In this exercise, you have a small CRUD application, which get a list of TODOS, update and delete some todos.
 
 Currently we have a working example but filled with lots of bad practices.
 

docs/src/content/docs/challenges/angular/8-pipe-pure.md

@@ -9,14 +9,27 @@ sidebar:
   order: 3
 ---
 
-The goal of this series of 3 pipe challenges is to master **pipe** in Angular.
-
-Pure pipes are a very useful way to transform data from your template. The difference between calling a function and a pipe is that pure pipes are memoized. So they won't be recalculated every change detection cycle if their inputs haven't changed.
-
 ## Information
 
-In this first exercice, you call a simple function inside your template. The goal is to convert it to a pipe.
+This is the first of three `@Pipe()` challenges, the goal of this series is to master **pipes** in Angular.
+
+Pipes are a very powerful way to transform data in your template. The difference between calling a function and a pipe is that pure pipes are memoized. So they won't be recalculated every change detection cycle if their inputs haven't changed.
+
+Pipes are designed to be efficient and optimized for performance. They use change detection mechanisms to only recalculate the value if the input changes, to minimize unnecessary calculations and improving rendering performance.
+
+By default a pipe is pure, you should be aware that setting `pure` to false is prone to be inefficient, because it increases the amount of rerenders.
+
+:::note
+A **pure** pipe is only called when the value changes.\
+A **impure** pipe is called every change detection cycle.
+:::
+
+There are some useful predefined pipes like the DatePipe, UpperCasePipe and CurrencyPipe. To learn more about pipes in Angular, check the API documentation [here](https://angular.io/guide/pipes).
+
+## Statement
+
+In this exercise, you need to refactor a transform function inside a component, which is called inside your template. The goal is to convert this function to a pipe.
 
 ## Constraints
 
-- must be strongly typed
+- Must be strongly typed

docs/src/content/docs/challenges/angular/9-pipe-wrapFn.md

@@ -9,15 +9,28 @@ sidebar:
   order: 103
 ---
 
-The goal of this series of 3 pipe challenges is to master **pipe** in Angular.
+## Information
 
-Pure pipes are a very useful way to transform data from your template. The difference between calling a function and a pipe is that pure pipes are memoized. So they won't be recalculated every change detection cycle if their inputs haven't changed.
+This is the second of three `@Pipe()` challenges, the goal of this series is to master **pipes** in Angular.
 
-## Information:
+Pipes are a very powerful way to transform data in your template. The difference between calling a function and a pipe is that pure pipes are memoized. So they won't be recalculated every change detection cycle if their inputs haven't changed.
 
-In this second exercice, you are calling multiple functions inside your template. You can create a specific pipe for each of the functions but this will be too cumbersome.
+Pipes are designed to be efficient and optimized for performance. They use change detection mechanisms to only recalculate the value if the input changes, to minimize unnecessary calculations and improving rendering performance.
+
+By default a pipe is pure, you should be aware that setting `pure` to false is prone to be inefficient, because it increases the amount of rerenders.
+
+:::note
+A **pure** pipe is only called when the value changes.\
+A **impure** pipe is called every change detection cycle.
+:::
+
+There are some useful predefined pipes like the DatePipe, UpperCasePipe and CurrencyPipe. To learn more about pipes in Angular, check the API documentation [here](https://angular.io/guide/pipes).
+
+## Statement
+
+In this exercise, you are calling multiple functions inside your template. You can create a specific pipe for each of the functions but this will be too cumbersome.
 The goal is to create a `wrapFn` pipe to wrap your callback function though a pipe. Your function MUST remain inside your component. **`WrapFn` must be highly reusable.**
 
 ## Constraints:
 
-- must be strongly typed
+- Must be strongly typed

docs/src/content/docs/challenges/ngrx/2-effect-selector.md

@@ -9,7 +9,7 @@ sidebar:
   order: 113
 ---
 
-For this exercice, you will have a dashboard of activities displaying the name, the main teacher and a list of subtitutes.
+For this exercise, you will have a dashboard of activities displaying the name, the main teacher and a list of subtitutes.
 
 ## Information
 

docs/src/content/docs/index.mdx

@@ -13,7 +13,7 @@ hero:
       icon: right-arrow
       variant: primary
     - text: Go to the latest Challenge
-      link: /challenges/angular/44-view-transition/
+      link: /challenges/angular/45-react-in-angular/
       icon: rocket
     - text: Give a star
       link: https://github.com/tomalaforge/angular-challenges

docs/src/content/docs/pt/challenges/angular/3-directive-enhancement.md

@@ -0,0 +1,46 @@
+---
+title: 🟠 Aprimoramento de Diretiva
+description: Desafio 3 é sobre o aprimoramento de uma diretiva nativa
+author: thomas-laforge
+challengeNumber: 3
+command: angular-ngfor-enhancement
+blogLink: https://medium.com/@thomas.laforge/ngfor-enhancement-716b44656a6c
+sidebar:
+  order: 101
+---
+
+:::note[Nota]
+Este exercício pode ser obsoleto com o novo controle de fluxo e do bloco de empty state dentro do bloco `@for`. No entanto, **diretivas estruturais** não serão removidas tão cedo, por isso você ainda pode aprender bastante com este exercício.
+:::
+
+## Informação
+
+Diretiva é uma ferramente poderosa oferecida pelo framework Angular. Você pode usar o princípio DRY compartilhando a lógica dentro de uma diretiva e aplicando ela em qualquer componente que quiser.
+
+Mas a verdadeira vantagem é que você consegue melhorar uma diretiva pré-existente que não **pertence** a você.
+
+## Declaração
+
+Neste exercício, queremos mostrar uma lista de pessoas. Se a lista está vazio, você deve mostrar _" the list is empty !! "_.
+
+Atualmente, temos:
+
+```typescript
+    <ng-container *ngIf="persons.length > 0; else emptyList">
+      <div *ngFor="let person of persons">
+        {{ person.name }}
+      </div>
+    </ng-container>
+    <ng-template #emptyList>The list is empty !!</ng-template>
+```
+
+Queremos nos livrar do `ng-container` escrevendo:
+
+```typescript
+    <div *ngFor="let person of persons; empty: emptyList">
+    {{ person.name }}
+    </div>
+    <ng-template #emptyList>The list is empty !!</ng-template>
+```
+
+Objetivo é **melhorar a diretiva ngFor**.

docs/src/content/docs/pt/challenges/angular/44-view-transition.md

@@ -6,7 +6,6 @@ challengeNumber: 44
 command: angular-view-transition
 sidebar:
   order: 208
-  badge: New
 ---
 
 ## Informação