|
Last change
on this file since 6a3a178 was 6a3a178, checked in by Ema <ema_spirova@…>, 3 years ago |
|
initial commit
|
-
Property mode
set to
100644
|
|
File size:
1.2 KB
|
| Line | |
|---|
| 1 | Creates and initializes a new Angular application that is the default project for a new workspace.
|
|---|
| 2 |
|
|---|
| 3 | Provides interactive prompts for optional configuration, such as adding routing support.
|
|---|
| 4 | All prompts can safely be allowed to default.
|
|---|
| 5 |
|
|---|
| 6 | - The new workspace folder is given the specified project name, and contains configuration files at the top level.
|
|---|
| 7 |
|
|---|
| 8 | - By default, the files for a new initial application (with the same name as the workspace) are placed in the `src/` subfolder. Corresponding end-to-end tests are placed in the `e2e/` subfolder.
|
|---|
| 9 |
|
|---|
| 10 | - The new application's configuration appears in the `projects` section of the `angular.json` workspace configuration file, under its project name.
|
|---|
| 11 |
|
|---|
| 12 | - Subsequent applications that you generate in the workspace reside in the `projects/` subfolder.
|
|---|
| 13 |
|
|---|
| 14 | If you plan to have multiple applications in the workspace, you can create an empty workspace by setting the `--create-application` option to false.
|
|---|
| 15 | You can then use `ng generate application` to create an initial application.
|
|---|
| 16 | This allows a workspace name different from the initial app name, and ensures that all applications reside in the `/projects` subfolder, matching the structure of the configuration file.
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
