-
Notifications
You must be signed in to change notification settings - Fork 11.9k
build: fix strict_deps for angular-cli test lib #29674
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
build: fix strict_deps for angular-cli test lib #29674
Conversation
ignore_strict_deps = True, | ||
deps = [ | ||
":angular-cli_rjs", | ||
":node_modules/@angular-devkit/core", |
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.
Would we prefer to move from the ts_project
dependency here to the npm package one?
Or should the clean up be to migrate to relative paths? If I understand/remember correctly, we want to use the npm package here so that we don't cross the npm package boundary with relative paths.
If there were imports from @angular/cli
those should be relative import paths instead though.
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.
This makes a lot of sense. It's just a leftover because apparently no runtime test broke (likely due to the transitive deps!!). My goal is to restrict/fix this and make it safe by leveraging Bazel visibility rules better
ignore_strict_deps = True, | ||
deps = [ | ||
":angular-cli_rjs", | ||
":node_modules/@angular-devkit/core", |
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.
This makes a lot of sense. It's just a leftover because apparently no runtime test broke (likely due to the transitive deps!!). My goal is to restrict/fix this and make it safe by leveraging Bazel visibility rules better
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. |
No description provided.