From f72782ee4c007e57cf4bfdd2d3dc92c518bf97f0 Mon Sep 17 00:00:00 2001 From: thomas Date: Wed, 18 Oct 2023 10:41:06 +0200 Subject: [PATCH] feat(): homogenise file directory --- apps/angular/bug-cd/README.md | 2 +- apps/performance/default-onpush/README.md | 2 +- apps/performance/memoized/README.md | 2 +- apps/performance/ngfor-biglist/README.md | 2 +- apps/performance/ngfor-optimize/README.md | 2 +- apps/performance/scroll-cd/README.md | 2 +- .../34/profiler-record.png | Bin .../35/memoize-profiler.png | Bin .../profiler-tab.png | Bin .../12-scroll-cd.md | 2 +- .../34-default-onpush.md | 4 ++-- .../35-memoize.md | 4 ++-- .../36-ngfor-optimize.md | 2 +- .../37-ngfor-biglist.md | 2 +- .../{angular-performance => performance}/index.mdx | 8 ++++---- libs/cli/src/generators/challenge/schema.json | 2 +- 16 files changed, 18 insertions(+), 18 deletions(-) rename docs/src/assets/{angular-performance => performance}/34/profiler-record.png (100%) rename docs/src/assets/{angular-performance => performance}/35/memoize-profiler.png (100%) rename docs/src/assets/{angular-performance => performance}/profiler-tab.png (100%) rename docs/src/content/docs/challenges/{angular-performance => performance}/12-scroll-cd.md (96%) rename docs/src/content/docs/challenges/{angular-performance => performance}/34-default-onpush.md (92%) rename docs/src/content/docs/challenges/{angular-performance => performance}/35-memoize.md (91%) rename docs/src/content/docs/challenges/{angular-performance => performance}/36-ngfor-optimize.md (95%) rename docs/src/content/docs/challenges/{angular-performance => performance}/37-ngfor-biglist.md (95%) rename docs/src/content/docs/challenges/{angular-performance => performance}/index.mdx (87%) diff --git a/apps/angular/bug-cd/README.md b/apps/angular/bug-cd/README.md index 2d1491e..b5f63f1 100644 --- a/apps/angular/bug-cd/README.md +++ b/apps/angular/bug-cd/README.md @@ -10,4 +10,4 @@ npx nx serve angular-bug-cd ### Documentation and Instruction -Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/angular-performance/32-angular-bug-cd/). +Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/performance/32-angular-bug-cd/). diff --git a/apps/performance/default-onpush/README.md b/apps/performance/default-onpush/README.md index f55ee50..72b8090 100644 --- a/apps/performance/default-onpush/README.md +++ b/apps/performance/default-onpush/README.md @@ -10,4 +10,4 @@ npx nx serve performance-default-onpush ### Documentation and Instruction -Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/angular-performance/34-default-onpush/). +Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/performance/34-default-onpush/). diff --git a/apps/performance/memoized/README.md b/apps/performance/memoized/README.md index 4e250b9..94feadd 100644 --- a/apps/performance/memoized/README.md +++ b/apps/performance/memoized/README.md @@ -10,4 +10,4 @@ npx nx serve performance-memoized ### Documentation and Instruction -Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/angular-performance/35-memoize/). +Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/performance/35-memoize/). diff --git a/apps/performance/ngfor-biglist/README.md b/apps/performance/ngfor-biglist/README.md index e23cb22..828f93e 100644 --- a/apps/performance/ngfor-biglist/README.md +++ b/apps/performance/ngfor-biglist/README.md @@ -10,4 +10,4 @@ npx nx serve performance-ngfor-biglist ### Documentation and Instruction -Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/angular-performance/37-ngfor-biglist/). +Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/performance/37-ngfor-biglist/). diff --git a/apps/performance/ngfor-optimize/README.md b/apps/performance/ngfor-optimize/README.md index 6571704..a26efa5 100644 --- a/apps/performance/ngfor-optimize/README.md +++ b/apps/performance/ngfor-optimize/README.md @@ -10,4 +10,4 @@ npx nx serve performance-ngfor-optimize ### Documentation and Instruction -Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/angular-performance/36-ngfor-optimize/). +Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/performance/36-ngfor-optimize/). diff --git a/apps/performance/scroll-cd/README.md b/apps/performance/scroll-cd/README.md index f8eaacf..ef30c5c 100644 --- a/apps/performance/scroll-cd/README.md +++ b/apps/performance/scroll-cd/README.md @@ -10,4 +10,4 @@ npx nx serve performance-scroll-cd ### Documentation and Instruction -Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/angular-performance/12-performance-scroll-cd/). +Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/performance/12-performance-scroll-cd/). diff --git a/docs/src/assets/angular-performance/34/profiler-record.png b/docs/src/assets/performance/34/profiler-record.png similarity index 100% rename from docs/src/assets/angular-performance/34/profiler-record.png rename to docs/src/assets/performance/34/profiler-record.png diff --git a/docs/src/assets/angular-performance/35/memoize-profiler.png b/docs/src/assets/performance/35/memoize-profiler.png similarity index 100% rename from docs/src/assets/angular-performance/35/memoize-profiler.png rename to docs/src/assets/performance/35/memoize-profiler.png diff --git a/docs/src/assets/angular-performance/profiler-tab.png b/docs/src/assets/performance/profiler-tab.png similarity index 100% rename from docs/src/assets/angular-performance/profiler-tab.png rename to docs/src/assets/performance/profiler-tab.png diff --git a/docs/src/content/docs/challenges/angular-performance/12-scroll-cd.md b/docs/src/content/docs/challenges/performance/12-scroll-cd.md similarity index 96% rename from docs/src/content/docs/challenges/angular-performance/12-scroll-cd.md rename to docs/src/content/docs/challenges/performance/12-scroll-cd.md index 8841dbb..540051e 100644 --- a/docs/src/content/docs/challenges/angular-performance/12-scroll-cd.md +++ b/docs/src/content/docs/challenges/performance/12-scroll-cd.md @@ -19,7 +19,7 @@ In this challenge, we only need to refresh the view at a specific scroll positio To have a better visualization of the problem, profile your application with Angular Dev Tools. :::note -If you don't know how to use it, read [the performance introduction page](/challenges/angular-performance/) first and come back after. +If you don't know how to use it, read [the performance introduction page](/challenges/performance/) first and come back after. ::: You can learn more details about zone pollution and how to resolve it [here](https://angular.io/guide/change-detection-zone-pollution). diff --git a/docs/src/content/docs/challenges/angular-performance/34-default-onpush.md b/docs/src/content/docs/challenges/performance/34-default-onpush.md similarity index 92% rename from docs/src/content/docs/challenges/angular-performance/34-default-onpush.md rename to docs/src/content/docs/challenges/performance/34-default-onpush.md index 6d4ec59..62c453c 100644 --- a/docs/src/content/docs/challenges/angular-performance/34-default-onpush.md +++ b/docs/src/content/docs/challenges/performance/34-default-onpush.md @@ -25,14 +25,14 @@ As you can see, each letter triggers a new change detection cycle, and all compo Let's use the Angular DevTool to profile our application and understand how this tool can help us understand what is happening inside our application. :::note -If you don't know how to use it, read [the performance introduction page](/challenges/angular-performance/) first and come back after. +If you don't know how to use it, read [the performance introduction page](/challenges/performance/) first and come back after. ::: Now, start profiling your application and type some letters inside the input field to trigger some change detection cycles. If you click on one of the bars (indicated by the yellow arrow in the picture below), you can see that `PersonListComponent`, `RandomComponent`, and all the `MatListItem` are impacted by the change detection cycle, even when we only interact with the input field. -![profiler record](../../../../assets/angular-performance/34/profiler-record.png 'Profiler Record') +![profiler record](../../../../assets/performance/34/profiler-record.png 'Profiler Record') ## Statement diff --git a/docs/src/content/docs/challenges/angular-performance/35-memoize.md b/docs/src/content/docs/challenges/performance/35-memoize.md similarity index 91% rename from docs/src/content/docs/challenges/angular-performance/35-memoize.md rename to docs/src/content/docs/challenges/performance/35-memoize.md index 5ea6788..86d321c 100644 --- a/docs/src/content/docs/challenges/angular-performance/35-memoize.md +++ b/docs/src/content/docs/challenges/performance/35-memoize.md @@ -27,14 +27,14 @@ We will not focus on the initial loading of the list in this challenge. Let's use the Angular DevTool to profile our application and understand how this tool can help us understand what is happening inside our application. :::note -If you don't know how to use it, read [the performance introduction page](/challenges/angular-performance/) first and come back after. +If you don't know how to use it, read [the performance introduction page](/challenges/performance/) first and come back after. ::: Now, start profiling your application and type some letters inside the input field. You will see some red bars showing up inside the profiler panel. If you click on one of the bars (indicated by the yellow arrow in the picture below), you will see that the change detection cycle is taking more than 3s in `PersonListComponent`. -![profiler record](../../../../assets/angular-performance/35/memoize-profiler.png 'Profiler Record') +![profiler record](../../../../assets/performance/35/memoize-profiler.png 'Profiler Record') ## Statement diff --git a/docs/src/content/docs/challenges/angular-performance/36-ngfor-optimize.md b/docs/src/content/docs/challenges/performance/36-ngfor-optimize.md similarity index 95% rename from docs/src/content/docs/challenges/angular-performance/36-ngfor-optimize.md rename to docs/src/content/docs/challenges/performance/36-ngfor-optimize.md index e8f2753..c05bf25 100644 --- a/docs/src/content/docs/challenges/angular-performance/36-ngfor-optimize.md +++ b/docs/src/content/docs/challenges/performance/36-ngfor-optimize.md @@ -21,7 +21,7 @@ We can also use the Angular DevTool to profile our application and unders :::note -If you don't know how to use it, read [the performance introduction page](/challenges/angular-performance/) first and come back after. +If you don't know how to use it, read [the performance introduction page](/challenges/performance/) first and come back after. ::: If you need more information about `NgFor`, I invite you to read the [documentation](https://angular.io/api/common/NgFor) first. diff --git a/docs/src/content/docs/challenges/angular-performance/37-ngfor-biglist.md b/docs/src/content/docs/challenges/performance/37-ngfor-biglist.md similarity index 95% rename from docs/src/content/docs/challenges/angular-performance/37-ngfor-biglist.md rename to docs/src/content/docs/challenges/performance/37-ngfor-biglist.md index 647575f..3240088 100644 --- a/docs/src/content/docs/challenges/angular-performance/37-ngfor-biglist.md +++ b/docs/src/content/docs/challenges/performance/37-ngfor-biglist.md @@ -18,7 +18,7 @@ We can use the Angular DevTool to profile our application and understand :::note -If you don't know how to use it, read [the performance introduction page](/challenges/angular-performance/) first and come back after. +If you don't know how to use it, read [the performance introduction page](/challenges/performance/) first and come back after. ::: ## Statement diff --git a/docs/src/content/docs/challenges/angular-performance/index.mdx b/docs/src/content/docs/challenges/performance/index.mdx similarity index 87% rename from docs/src/content/docs/challenges/angular-performance/index.mdx rename to docs/src/content/docs/challenges/performance/index.mdx index 27af452..de7b508 100644 --- a/docs/src/content/docs/challenges/angular-performance/index.mdx +++ b/docs/src/content/docs/challenges/performance/index.mdx @@ -20,7 +20,7 @@ This extension allows you to profile your application and detect performance iss When you serve an Angular application, you can inspect a page by pressing F12, which will open the Chrome developer tools. Then navigate to the Angular tab. From there, you can select the Profiler tab as shown below. -![profiler tab](../../../../assets/angular-performance/profiler-tab.png 'Profiler tab') +![profiler tab](../../../../assets/performance/profiler-tab.png 'Profiler tab') You can now profile your application by clicking on the record button. You can play with your application and see when change detection is triggered and which components are rerendered. @@ -33,17 +33,17 @@ Now that you know how to use the Angular DevTool, you can choose a challe diff --git a/libs/cli/src/generators/challenge/schema.json b/libs/cli/src/generators/challenge/schema.json index 955d72d..b1078e3 100644 --- a/libs/cli/src/generators/challenge/schema.json +++ b/libs/cli/src/generators/challenge/schema.json @@ -68,7 +68,7 @@ "label": "Angular" }, { - "value": "angular-performance", + "value": "performance", "label": "Angular Performance" }, {