Angular: Understanding Modules and Services

Understanding Modules And Services

You are here! You started to feel comfortable with this and suddenly.

I have found that most developers are struggling with these problems, as they do not have a clear idea about how the angular module works and the importance of technical dependency injection.

Types of activities

In the corner, everything that is not AppModule is a technical module with the following warnings:
You must list all the subjects, the directives, and the pipes that they need
If you want to use part of the module, you must write it in a specific section. It also applies to rules and pipes.
Provide CommonModule instead of the browser module
With BrowserModule put in AppModule (which is required to run the application in a browser), module this can bring to other places, instead, we have to formulate CommonModule including standard instructions in English, such as ngIf, for, ngClass, etc. browser module also re-exports common module so it can be used as AppModule guidelines.
The only module that is responsible for starting the section is AppModule!
For the determination of the points of view of all, we use functional modules, since each point of view (or to) the own module! Since we are talking about the site, we are also talking about deceptive. Any "visual" (calling method) can be a lazy router.

core module

The answer to the question "Where do I provide my international services?" It will be AppModule. This is because the services are used, which means that it is available anywhere.

But I really do not want our AppModule to be completed with chaos ... Angular recommends that all international services be delivered to a special module called CoreModule, and only imported into AppModule.

Shared module

A shared module is ideal for application components that can be used, so do not re-import the module parts, but the module will import action.

• In our AppModule, we will create a shared module with connected providers
• All other parts imported without this module will receive the AppModule already received

important of services

Therefore, our services can include 4 different locations:
• in CoreModule, which will have our international service and one year
• SharedModule, which will provide the services that need it
• "Module view" if the service only needs the module
• Parts, if you only need it there

The last situation

We have talked a lot about the modules, but there is also much more that could be well structured. We can:
• Write small pieces of microcomponents instead of locks
• Use ChangeDetection.OnPush on our paperless parts, to avoid Looga common power concepts (but carefully)
• Use router protection to protect our roads
• Use the Looga resolution path to eliminate dependency on the modules to see
• Use web pages to handle logical identities and other things
• Use the library as Redux or MobX to manage business records of all applications.

To getting expert-level training for Angularjs Training in your location-Angularjs training in Chennai| Angularjs training in Chennai | Angularjs training in Chennai  | Angularjs training in Velachery | Angularjs training in Tambaram | Angularjs training in sholinganallur | Angularjs training in Annanagar | Angularjs training in Bangalore | Angularjs training in Bangalore | Angularjs training in btm | Angularjs training in marathahalli | Angularjs training in electronic city | for getting online training Angularjs online training| Angularjs training in USA