-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Migrate ng_module
#30731
Merged
Merged
Migrate ng_module
#30731
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ae80087
to
46ebd2b
Compare
Sets up the new `ng_project` rule and uses it in `cdk/a11y`. Also sets up this rule similar to our `ts_project` interop- reusing that code completely, yay!
With the new `ts_project`, or `ng_project` rule, HTML templates of components are also copied over to the bazel bin. This unveiled a naming conflict of e.g. `slider.md` being generated as `slider.html`; while there is a template like `slider.html`.
This commit migrates all `ng_module` targets to the new `ng_project` rule. This change was partially assisted/generated using Gemini.
Currently we always use our build tsconfigs from `/src`, whenever we see a `ts_project`, or `ng_project` target. This doesn't work for targets outside of `src` and ambiguously breaks the build. This commit makes this a more obvious failure mode.
We've decided that this size testing infra is not useful after the MDC migration and can be removed; we can easily re-add if we want. Notably it was disabled/not running on CI (in a blocking mode) for months.
Temporarily patches the legacy `ng_package` rule to properly request partial compilation output from the new `ng_project` rule targets.
This commit removes references to the `ng_module` rule.
josephperrott
approved these changes
Mar 27, 2025
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
I like how we were able to just slot in the ng_project
rule as the actual rule impl that the macro references and keep everything else the same.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
action: merge
The PR is ready for merge by the caretaker
area: build & ci
Related the build and CI infrastructure of the project
target: patch
This PR is targeted for the next patch release
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See individual commits