dev:angular_dev_best_practices
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
dev:angular_dev_best_practices [2024/09/14 11:14] – Add more details about ng lint sandbergja | dev:angular_dev_best_practices [2024/09/15 13:03] (current) – [Running ng lint] add info about prerequisites sandbergja | ||
---|---|---|---|
Line 42: | Line 42: | ||
You should run ng lint early and often in the development process, as it can help you avoid certain bugs. Definitely run it before submitting your code for community review, or before committing any Angular code to the Evergreen repository. | You should run ng lint early and often in the development process, as it can help you avoid certain bugs. Definitely run it before submitting your code for community review, or before committing any Angular code to the Evergreen repository. | ||
+ | |||
+ | == Preparing to run ng lint == | ||
+ | |||
+ | Ng lint does not require a running Evergreen system. | ||
+ | |||
+ | - [[newdevs: | ||
+ | - [[https:// | ||
+ | - In a new terminal, cmd, or powershell window, use the cd command to navigate to the Open-ILS/ | ||
+ | - Run the command '' | ||
+ | - Optionally, install the Angular cli globally with '' | ||
+ | |||
+ | |||
+ | == Running the ng lint command == | ||
+ | |||
* If you have the Angular cli installed, you can run the following command from the eg2 directory: '' | * If you have the Angular cli installed, you can run the following command from the eg2 directory: '' |
dev/angular_dev_best_practices.txt · Last modified: 2024/09/15 13:03 by sandbergja