Skip to content

How does core.module.ts work? #29

@Jan-PeterRichterCG

Description

@Jan-PeterRichterCG

Category: enhancement

Severity: High

Description of issue / expected enhacement /Comments
The tutorial recommends to create a file core.module.ts in order to bundle large amounts of dependencies into one file (component?). See https://github.com/devonfw/devonfw-tutorial-sources/wiki/build-devon4ng-application#root-component

In order to be able to use covalent and angular mats, we are going to create a core module that we will import in every module where we want to use covalent and angular.

Later on, it is said that ...

if you decide to use a component that is not included here, you need to add the corresponding module of the component here.

Problem: how do I add a module, especially, what are the rules for adding it to imports, exports and/or providers?
Example: Why is CovalentMediaModule in importsAND exports while CovalentChipsModule is only in exports? Why is HttpClientModule in exports and providers but not in imports?
If I want to add CovalentStepsModule do I have to add it to imports, to exports and/or providers?

Your environment - windows/Linux, Devonfw version , component

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions