-
-
Notifications
You must be signed in to change notification settings - Fork 7.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(core): always bind global modules when scan for modules #12880
base: master
Are you sure you want to change the base?
Conversation
packages/core/scanner.ts
Outdated
if (this.isForwardReference(moduleDefinition)) { | ||
moduleDefinition = (moduleDefinition as ForwardReference).forwardRef(); | ||
const moduleInstance = await this.insertModule(moduleDef, scope); | ||
this.container.bindGlobalsToImports(moduleInstance); |
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.
bindGlobalsToImports
should be called only for lazy modules.
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.
Will create parameter whether modules bind to global
Could you create release branch for 9.x so this branch merged? |
Just fyi, in case you're blocked by this change you can always use |
@5d-jh can you please rebase your branch |
@micalevisk Because this pr resolves issue on v9, this pr should be merged into v9 release branch which is currently not exist. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #12879
What is the new behavior?
Scanning for modules always bound for global modules,
Does this PR introduce a breaking change?
Other information
This branch is based on 9.4.3. Hence should not be merged into master.