Skip to content

build: resolve module names in circular deps test #18957

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

Conversation

devversion
Copy link
Member

Currently the circular dependencies test only resolves
relative imports. It does not resolve module names
to packages/entry-points which are part of the Angular
Components repository.

To ensure that such repo-specific module names are resolved, we
add a custom module resolver. This helps us making the circular deps
test future-proof in case an entry-point uses module names.

Within an entry-point circular dependencies could be also created
with module name imports.

@josephperrott Sorry. I would have commented on the original PR, but I didn't have a chance to have anther look as the PR still had merge ready applied and got merged quickly.

Currently the circular dependencies test only resolves
relative imports. It does not resolve module names
to packages/entry-points which are part of the Angular
Components repository.

To ensure that such repo-specific module names are resolved, we
add a custom module resolver. This helps us making the circular deps
test future-proof in case an entry-point uses module names.

Within an entry-point circular dependencies could be also created
with module name imports.
@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels Mar 31, 2020
@devversion devversion requested a review from jelbourn as a code owner March 31, 2020 16:33
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 31, 2020
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added lgtm action: merge The PR is ready for merge by the caretaker labels Mar 31, 2020
@jelbourn
Copy link
Member

Joey's partially OOO today, so I'll merge this now and we can do a follow-up if he proposes any changes

@jelbourn jelbourn merged commit 2fce0c6 into angular:master Mar 31, 2020
jelbourn pushed a commit that referenced this pull request Mar 31, 2020
Currently the circular dependencies test only resolves
relative imports. It does not resolve module names
to packages/entry-points which are part of the Angular
Components repository.

To ensure that such repo-specific module names are resolved, we
add a custom module resolver. This helps us making the circular deps
test future-proof in case an entry-point uses module names.

Within an entry-point circular dependencies could be also created
with module name imports.

(cherry picked from commit 2fce0c6)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants