mirror of
https://github.com/Raghu-Ch/angular-challenges.git
synced 2026-02-10 12:53:03 -05:00
Merge pull request #586 from svenson95/fix-typos
docs: fix exercice typo in docs french to english
This commit is contained in:
@@ -14,7 +14,7 @@ Pure pipes are a very useful way to transform data from your template. The diffe
|
||||
|
||||
## Information:
|
||||
|
||||
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.
|
||||
In this third 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:
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -10,7 +10,7 @@ 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
|
||||
@@ -21,7 +21,7 @@ But the real power is that you can enhance an already existing directive which m
|
||||
|
||||
## 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:
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ Pure pipes are a very useful way to transform data from your template. The diffe
|
||||
|
||||
## Information
|
||||
|
||||
In this first exercice, you call a simple function inside your template. The goal is to convert it to a pipe.
|
||||
In this first exercise, you call a simple function inside your template. The goal is to convert it to a pipe.
|
||||
|
||||
## Constraints
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ Pure pipes are a very useful way to transform data from your template. The diffe
|
||||
|
||||
## Information:
|
||||
|
||||
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.
|
||||
In this second 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:
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user