Repository navigation
fix(@schematics/angular): use enableIvy as true - #13626
Merged
Merged
Conversation
filipesilva
added
the
target: major
filipesilva
force-pushed
the
enableivy-true
branch
from
February 20, 2019 12:49
1e937ca to
5dcd70b
Compare
clydin
approved these changes
Feb 20, 2019
clydin
left a comment
clydin
left a comment
Member
There was a problem hiding this comment.
LGTM. Couple CI failures though. Not sure if they are related.
Contributor
Author
|
The test-large isn't but the e2e is. I think this PR needs to wait for the next release of angular to use that in the e2e test. |
filipesilva
force-pushed
the
enableivy-true
branch
from
February 22, 2019 15:35
5dcd70b to
b803fc4
Compare
|
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. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Blocked on angular/angular#28616