-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
fix(ivy): @Component should support entry components from another module #29566
Conversation
@@ -158,6 +158,7 @@ function verifySemanticsOfNgModuleDef(moduleType: NgModuleType): void { | |||
const errors: string[] = []; | |||
const declarations = maybeUnwrapFn(ngModuleDef.declarations); | |||
const imports = maybeUnwrapFn(ngModuleDef.imports); | |||
flatten(imports, unwrapModuleWithProvidersImports).forEach(verifySemanticsOfNgModuleDef); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not: we've got another flatten
here:
export function flatten(list: any[]): any[] { |
I know that the code duplication was here before but maybe a good occasion to remove it? (just note that the flatten
I'm referring to returns a new array instead of writing to the out
one - which I find easier to follow!)
Without the fix, the test would fail with:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but please take care of @pkozlowski-opensource comment.
a27e227
to
adba699
Compare
@pkozlowski-opensource @mhevery I've updated the PR to remove the code duplication, PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Spotted while analysing failures in ng-bootstrap tests