feat(challenge25): extends Nx custom library

This commit is contained in:
thomas
2023-06-19 22:09:54 +02:00
parent bcf44956f9
commit c9efdea85e
48 changed files with 333 additions and 35 deletions

View File

@@ -15,7 +15,7 @@ You begin with an application that has basic navigation and anchor navigation in
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve anchor-scrolling`
5. _...work on it_
6. Commit your work

View File

@@ -36,7 +36,7 @@ But in this part, we can pass to ListComponent, a list of **any object**. And we
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve context-outlet-type**
5. _...work On it_
6. Commit your work

View File

@@ -41,7 +41,7 @@ Good luck !!! 💪
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve create-harness`
5. _...work on it_
6. Commit your work

View File

@@ -26,10 +26,7 @@ What you will need to do:
this.todos[todoUpdated.id - 1] = todoUpdated;
// Prefer something like this, but need to be improved because we still want the same order
this.todos = [
...this.todos.filter((t) => t.id !== todoUpdated.id),
todoUpdated,
];
this.todos = [...this.todos.filter((t) => t.id !== todoUpdated.id), todoUpdated];
```
- Use **ChangeDectection.OnPush**
@@ -53,7 +50,7 @@ this.todos = [
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve crud**
5. _...work On it_
6. Commit your work

View File

@@ -18,7 +18,7 @@
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve declarative-to-reactive**
5. _...work on it_
6. Commit your work

View File

@@ -23,7 +23,7 @@ One way to achieve this is by adding a second argument to the pipe, but this is
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve di`
5. _...work on it_
6. Commit your work

View File

@@ -38,7 +38,7 @@ The goal is to **improve the ngFor directive**
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve ngfor-enhancement**
5. _...work On it_
6. Commit your work

View File

@@ -28,7 +28,7 @@ In NgRx, **selectors** is a very powerful tool often **misused**. You should use
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve ngrx-1**
5. _...work On it_
6. Commit your work

View File

@@ -29,7 +29,7 @@ the application contain a root route, a lazy loaded route and a component with a
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve ngrx-notification**
5. _...work on it_
6. Commit your work

View File

@@ -20,7 +20,7 @@ To achieve this, we will use overload functions.
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **`npx nx serve overload`**
5. _...work on it_
6. Commit your work

View File

@@ -51,7 +51,7 @@ In **Routes.ts**, route all user to the correct **DashboardComponent** using **C
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve permissions**
5. _...work on it_
6. Commit your work

View File

@@ -18,7 +18,7 @@ In this first exercice, you add calling a simple function inside your template.
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve pipe-easy`
5. _...work on it_
6. Commit your work

View File

@@ -18,7 +18,7 @@ In this third exercice, you want to access utils functions. Currently we cannot
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve pipe-hard`
5. _...work on it_
6. Commit your work

View File

@@ -19,7 +19,7 @@ The goal is to create a `wrapFn` pipe to wrap your callback function though a pi
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve pipe-intermediate`
5. _...work on it_
6. Commit your work

View File

@@ -18,7 +18,7 @@ Implement the City card.
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve projection**
5. _...work on it_
6. Commit your work

View File

@@ -10,7 +10,7 @@ In this small application, you can pass data though routing to `TestComponent`.
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve router-input`
5. _...work on it_
6. Commit your work

View File

@@ -26,7 +26,7 @@ The QA team reports a **bug**. The UI shows **All [topic] have been deleted** al
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve rxjs-pipe-bug`
5. _...work on it_
6. Commit your work

View File

@@ -24,7 +24,7 @@ WATCH MODE : `npx nx component-test rxjs-race-condition --watch`
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve rxjs-race-condition`
5. _...work on it_
6. Commit your work

View File

@@ -27,7 +27,7 @@ You cannot opt-out of zone.js. If this code is part of a large project and you o
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve scroll-cd**
5. _...work on it_
6. Commit your work

View File

@@ -18,7 +18,7 @@ In this challenge, you will need to use both CSS variables and :host-context to
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. **nx serve styling**
5. _...work on it_
6. Commit your work

View File

@@ -22,7 +22,7 @@ I created some `it` blocks but feel free to add more test if you like to. -->
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve testing-forms` to play with the application
5. `npx nx test testing-forms` to test your application with Testing Library
6. `npx nx component-test testing-forms --watch` to test your application with Cypress

View File

@@ -17,7 +17,7 @@ Documentation for Angular Material component is [here](https://material.angular.
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve testing-harness` to play with the application
5. `npx nx test testing-harness` to test your application with Testing Library
6. _...work on it_

View File

@@ -19,7 +19,7 @@ I created some `it` blocks but feel free to add more test if you like to.
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve testing-input-output` to play with the application
5. `npx nx test testing-input-output` to test your application with Testing Library
6. `npx nx component-test testing-input-output --watch` to test your application with Cypress

View File

@@ -22,7 +22,7 @@ I created some `it` blocks but feel free to add more test if you like to.
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve testing-modal` to play with the application
5. `npx nx test testing-modal` to test your application with Testing Library
6. `npx nx component-test testing-modal --watch` to test your application with Cypress

View File

@@ -20,7 +20,7 @@ I created some `it` blocks but feel free to add more test if you like to.
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve testing-nested` to play with the application
5. `npx nx test testing-nested` to test your application with Testing Library
6. `npx nx component-test testing-nested --watch` to test your application with Cypress

View File

@@ -26,7 +26,7 @@ I created some `it` blocks but feel free to add more test if you like to.
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve testing-router-outlet` to play with the application
5. `npx nx test testing-router-outlet` to test your application with Testing Library
6. `npx nx component-test testing-router-outlet --watch` to test your application with Cypress

View File

@@ -22,7 +22,7 @@ I created some `it` blocks but feel free to add more test if you like to. -->
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve testing-table` to play with the application
5. `npx nx test testing-table` to test your application with Testing Library
6. `npx nx component-test testing-table --watch` to test your application with Cypress

View File

@@ -22,7 +22,7 @@ I created some `it` blocks but feel free to add more test if you like to. -->
1. Fork the project
2. clone it
3. npm install
3. npm ci
4. `npx nx serve testing-todos-list` to play with the application
5. `npx nx test testing-todos-list` to test your application with Testing Library
6. `npx nx component-test testing-todos-list --watch` to test your application with Cypress