-
Notifications
You must be signed in to change notification settings - Fork 6.8k
build: migrate to new --define=angular_ivy_enabled flag #17792
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
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.
Nice. I like it. It's currently blocked on a new Angular release?
.bazelrc
Outdated
@@ -40,9 +40,10 @@ build:release --workspace_status_command="node ./tools/bazel-stamp-vars.js" | |||
################################ | |||
# View Engine / Ivy toggle # | |||
################################ | |||
build --define=angular_ivy_enabled=True |
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.
We can avoid the duplication by using common --config=ivy
2114a88
to
af557aa
Compare
Remove all usage of --define=compile=* within the repo, using --config=ivy and --config=view-engine instead. This matches the changes in the angular/angular repo and is clearer to developers what the flag is actually doing.
af557aa
to
c62d237
Compare
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. |
Remove all usage of --define=compile=* within the repo, using --config=ivy and
--config=view-engine instead. This matches the changes in the angular/angular
repo and is clearer to developers what the flag is actually doing.