vcgit-forge/angular-challenges
1
0
Fork 0
mirror of https://github.com/Raghu-Ch/angular-challenges.git synced 2026-02-11 13:23:02 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #372 from Sagardevkota/fix/typo_and_command

Browse Source 
Fix/typo and command
This commit is contained in:
Laforge Thomas
2023-11-27 12:16:38 +01:00
committed by GitHub
parent 36ad018f92 da325dc827
commit 83b0ebedae
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/src/content/docs/challenges/nx/26-generator-comp.md
View File

@@ -15,7 +15,7 @@ WIP: The following documentation will be reviewed and improved. However, you can
Welcome to the marvelous world of Nx generators.
Generators are awesome tools that can help you and your team generate code more quickly, especially for pieces of code that you use frequently. Inside an entreprise project, you often have to create components that look similar. And most of the time, you end up copy/pasting other components. In Nx, you can create this boilerplate in a simple command using generators.
Generators are awesome tools that can help you and your team generate code more quickly, especially for pieces of code that you use frequently. Inside an enterprise project, you often have to create components that look similar. And most of the time, you end up copy/pasting other components. In Nx, you can create this boilerplate in a simple command using generators.
## Statement

2
docs/src/content/docs/challenges/testing/20-modal.md
View File

@@ -14,7 +14,7 @@ In this small application, you have an input prompting you to enter a name, and
If you enter a name, a confirmation modal will appear; otherwise an error modal will be displayed.
In the confirmation modal, if you click the **Confirm** button, a message confirming the submission of the form will appear. If the user clicks on **Cancel**, an error message will be displayed.
The goal of this challenge is to test the dialogs inside your application. To do so, we will test the full application like an end-to-end test will do. This means, we will test the `AppComponent` as a black box and react to events on the page. <b>No internal details should be tested</b>. The difference between an e2e test and integration test is that we will mock all API calls. _(All http requests are faked inside this application, but this would not be the case in a real entreprice application.)_
The goal of this challenge is to test the dialogs inside your application. To do so, we will test the full application like an end-to-end test will do. This means, we will test the `AppComponent` as a black box and react to events on the page. <b>No internal details should be tested</b>. The difference between an e2e test and integration test is that we will mock all API calls. _(All http requests are faked inside this application, but this would not be the case in a real enterprise application.)_
You can play with it by running : `npx nx serve testing-modal`.