Repository navigation
test: add comprehensive tests for Ivy lazy load styles - #13774
Merged
Merged
Conversation
filipesilva
added
the
target: major
14 tasks
filipesilva
force-pushed
the
ivy-lazy-load
branch
5 times, most recently
from
February 26, 2019 18:42
4c387df to
843b753
Compare
filipesilva
force-pushed
the
ivy-lazy-load
branch
from
February 27, 2019 09:48
843b753 to
9a78d78
Compare
alan-agius4
reviewed
Feb 27, 2019
alan-agius4
reviewed
Feb 27, 2019
alan-agius4
reviewed
Feb 28, 2019
filipesilva
force-pushed
the
ivy-lazy-load
branch
from
February 28, 2019 11:19
9a78d78 to
042b629
Compare
filipesilva
force-pushed
the
ivy-lazy-load
branch
from
February 28, 2019 13:07
042b629 to
f524912
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.
Context on these usecases can be found here: angular/angular#28685 (comment)