mirror of
https://github.com/ionic-team/ionic-framework.git
synced 2025-08-16 10:01:59 +08:00
test(angular): disable .angular cache (#26962)
This commit is contained in:
@ -4,7 +4,7 @@ Ionic Framework supports multiple versions of Angular. As a result, we need to v
|
|||||||
|
|
||||||
## Application Cache
|
## Application Cache
|
||||||
|
|
||||||
Angular CLI creates a cache of several files on disk by default in the `.angular` directory. This decreases the time taken to build the test application. When testing changes by directly modifying Ionic's source code in `node_modules`, you may need to manually clear the `.angular` cache and restart the local server every time you make a change. As a result, it may be desirable to disable the `.angular` cache while making changes to the code.
|
Angular CLI creates a cache of several files on disk by default in the `.angular` directory. This decreases the time taken to build the test application. However, the cache makes it difficult to quickly sync and check local changes of Ionic. As a result, the `.angular` cache is disabled by default in the test app projects.
|
||||||
|
|
||||||
See https://angular.io/cli/cache for more information.
|
See https://angular.io/cli/cache for more information.
|
||||||
|
|
||||||
@ -22,6 +22,8 @@ ng cache disable
|
|||||||
ng cache enable
|
ng cache enable
|
||||||
```
|
```
|
||||||
|
|
||||||
|
> Note: You will need to delete the `.angular` cache and restart the dev server every time you want to sync local changes of Ionic.
|
||||||
|
|
||||||
## Test App Build Structure
|
## Test App Build Structure
|
||||||
|
|
||||||
Unlike other test applications, these test apps are broken up into multiple directories. These directories are then combined to create a single application. This allows us to share common application code, tests, etc so that each app is being tested the same way. Below details the different pieces that help create a single test application.
|
Unlike other test applications, these test apps are broken up into multiple directories. These directories are then combined to create a single application. This allows us to share common application code, tests, etc so that each app is being tested the same way. Below details the different pieces that help create a single test application.
|
||||||
@ -86,4 +88,4 @@ Note: You may encounter some other peer dependency issues not covered by the Ang
|
|||||||
7. Open `./github/workflows/build.yml` and find the `test-angular-e2e` job.
|
7. Open `./github/workflows/build.yml` and find the `test-angular-e2e` job.
|
||||||
8. Find the `apps` field under `matrix`.
|
8. Find the `apps` field under `matrix`.
|
||||||
9. Add "ng14" to the `apps` field.
|
9. Add "ng14" to the `apps` field.
|
||||||
10. Committ these changes and push.
|
10. Commit these changes and push.
|
||||||
|
@ -143,6 +143,9 @@
|
|||||||
"cli": {
|
"cli": {
|
||||||
"schematicCollections": [
|
"schematicCollections": [
|
||||||
"@angular-eslint/schematics"
|
"@angular-eslint/schematics"
|
||||||
]
|
],
|
||||||
|
"cache": {
|
||||||
|
"enabled": false
|
||||||
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
Reference in New Issue
Block a user