Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How does core.module.ts work? #29

Open
Jan-PeterRichterCG opened this issue Mar 22, 2019 · 0 comments
Open

How does core.module.ts work? #29

Jan-PeterRichterCG opened this issue Mar 22, 2019 · 0 comments

Comments

@Jan-PeterRichterCG
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant