Angular CLI operation blueprint parsing code

This time I will bring you the Angular CLI operation blueprint parsing code. What are the precautions for the Angular CLI operation blueprint parsing code? The following is a practical case, let’s take a look.

ng generate command.

The format of this command is ng generate .

You can also use the --dry-run parameter to list the files to be generated instead of actually generating them.

For example:

ng generate component person, a person will be generated .component.ts.

ng generate service sales-data will generate a sales-data.service.ts.

ng generate class user-model will generate a user-model.ts Inside is the UserModel class.

Components.

ng The command to generate xxx xxx is still a bit long. Here angular cli has built-in aliases for the command, for example:

ng generate component person In this command, the generate in

can be replaced by the letter g, and the component in

can be replaced by the letter c.

So these two commands are equal:

ng generate component person
ng g c person

You can go here to view component-related commands and aliases:

https://github.com/angular/angular-cli/wiki/ generate-component

Possibly commonly used command parameters are:

1. --flat indicates whether there is no need to create a folder

2. --inline-template (-it) Whether the template should be placed in the ts file

3. --inline-style (-is) Whether the style should be placed in the ts file.

4. --spec Do you need to create a spec file (test file)

5. --view-encapsulation (-ve) View Encapsulation strategy (simply understood as style File scope policy).

6. --change-detection (-cd) Change detection policy.

7. --prefix Set this The prefix of component

8. --dry-run (-d) prints out the generated file list instead of directly generating it.

See For the following two pairs of commands with the same effect, it is more convenient to use aliases:

ng generate component person
ng generate component person --inline-template --inline-style
ng g c person
ng g c person -it -is

Let’s try these commands:

Create the project: ng new my-app Wait until npm install is completed before proceeding.

After establishing the project, enter the directory and execute the command:

ng g c person -d

This command will generate the above 4 files and updateapp.module.ts.

Remove the -d parameter below and generate the file:

You can see that the file is generated in the project. And app.module.ts has been updated, and the component declaration has been made in it.

Try to generate another component again, using some parameters View Encapsulation and Change Detection Strategy:

ng g c student -ve Emulated -cd OnPush

You can see that the parameters work.

Through the source code management page, you can see that these two commands affect the app. What updates have been made to the module:

Declare the two generated components respectively.

Then I commit...

Directive.

ng g d filter-box -d

This is the file report, the actual generation below:

ng g d filter-box

Through the source code management of vscode, you can see the changes:

directive生成了两个文件和component一样, 也在app.module进行了声明.

看一下目录结构:

生成的directive的结构是没有目录, 也就是flat的.

如果不想生成flat样式的, 想让其拥有自己的文件夹, 那么就是用--flat参数:

ng g d filter-box2 --flat false

这样就有自己的文件夹了.

commit一下.

Service.

ng g s order-data -d

可以看到 这个命令会生成flat结构的service.

然后把-d去掉, 真实生成文件:

ng g s order-data

可以从源码管理看到, 只生成了两个文件, 并没有在app.module里面注册:

当然可以在这里写代码把刚才生成的service注册进去.

但是正确的做法是使用 -m 参数来指定需要注册的module:

ng g s order-data2 -m app

这次生成的order-data2 service就会在app.module.ts里面进行注册了.

然后再commit一下.

Model/Interface/Enum/Pipe.

model:

ng g cl models/user

这个命令会创建models文件夹, 然后在里面创建user这个model:

interface:

ng g i models/animal

enum:

ng g e models/gender

commit一下.

Pipe.

ng g p camel-case

除了生成两个文件之外, 这个命令默认也会更新app.module.

Module.

ng g m login

可以看到module默认是自带文件夹的.

然后我试试添加一个component, 目的是要在login module进行声明:

可以看到我要创建的welcome component默认是在app.module里面进行声明的, 这时候如果想要在login module进行声明, 就要使用 -m 参数:

去掉-d执行生成命令后:

I believe you have mastered the method after reading the case in this article. For more exciting information, please pay attention to other related articles on the php Chinese website!

Recommended reading:

Detailed explanation of unit and E2E testing steps with Angular CLI

Place the mouse on the text to pop up the floating layer

The above is the detailed content of Angular CLI operation blueprint parsing code. For more information, please follow other related articles on the PHP Chinese website!