Skip to content

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

Merged
merged 1 commit into from
Dec 3, 2019

Conversation

josephperrott
Copy link
Member

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.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 22, 2019
Copy link
Member

@devversion devversion left a 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
Copy link
Member

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

@devversion devversion added pr: lgtm blocked This issue is blocked by some external factor, such as a prerequisite PR labels Nov 25, 2019
@devversion devversion removed the blocked This issue is blocked by some external factor, such as a prerequisite PR label Nov 28, 2019
@josephperrott josephperrott force-pushed the new-ivy-define-flag branch 2 times, most recently from 2114a88 to af557aa Compare December 3, 2019 23:16
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.
@josephperrott josephperrott marked this pull request as ready for review December 3, 2019 23:21
@josephperrott josephperrott requested review from jelbourn and a team as code owners December 3, 2019 23:21
@josephperrott josephperrott added action: merge The PR is ready for merge by the caretaker pr: merge safe target: patch This PR is targeted for the next patch release target: major This PR is targeted for the next major release labels Dec 3, 2019
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 merged commit 03a9c1d into angular:master Dec 3, 2019
@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 Jan 3, 2020
@josephperrott josephperrott deleted the new-ivy-define-flag branch March 20, 2020 22:15
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: major This PR is targeted for the next major release 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