Skip to content

refactor(snack-bar): rework to account for ivy #15537

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

Closed
wants to merge 44 commits into from

Conversation

crisbeto
Copy link
Member

Ivy equivalent of #15536.

Reworks the snack bar to account for a breaking change in Ivy.

alxhub and others added 30 commits January 10, 2019 11:56
See scripts/ivy/README.md for instructions.
This makes the unit tests runnable on the ivy-2019 branch by making the
following changes:
* Use the unminified umd bundles. The minified bundles fail due to some
yet indeterminate bug.
* Update the install script to be platform independent (formerly only
worked on macOS)
* Skip the tree tests. Something about the tree tests crashes the test
runner.
This is necessary to run `bazel` on Angular's CI
This should fix the tests for AriaDescriber, AutofillMonitor, Portal,
BottomSheet, Autocomplete, and Drawer.
Reworks a test that depends on static queries and fails under Ivy.
* Fixes one unit test that was depending on static queries.
* Fixes the remaining 16 failures that were due to some code that was commented out while waiting for a task which was resolved.
This makes the test pass in ivy (as well as ViewEngine) since attribute
bindings are set during creating mode in ivy.
…r#15309)

This makes a test pass both with ivy and ViewEngine
jelbourn and others added 14 commits February 26, 2019 09:25
Fixes some tests that will fail under Ivy, because they depend on static queries.
…15330)

Fixes some tests that fail under Ivy, because they depend on static queries.
…inserting (angular#15359)

* fix(virtual-scroll): move views that are already attached instead of inserting

* fix: add more static queries for cdk virtual scroll

* refactor(button): use [attr.disabled] host binding in MatButton

With ivy, MatAnchor will inherit the host bindings of MatButton. The
`[disabled]` binding would then be an error since HTMLAnchorElement does
not have a `disabled` property. To work around this, we can simply use
the `disabled` attribute instead, which will always be reflected back
into the property when it exists.

Also add a missing `fixture.detectChanges()` to a test.
Fixes the chip list tests that are failing under Ivy due to a known breaking change.
Reworks the snack bar to account for a breaking change in Ivy.
@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround pr: merge safe labels Mar 19, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 19, 2019
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Mar 19, 2019
@ngbot
Copy link

ngbot bot commented Mar 19, 2019

I see that you just added the pr: merge ready label, but the following checks are still failing:
    failure status "ci/circleci: api_golden_checks" is failing
    failure status "ci/circleci: bazel_build_test" is failing
    failure status "ci/circleci: build_release_packages" is failing
    failure status "ci/circleci: e2e_tests" is failing
    failure status "ci/circleci: lint" is failing
    failure status "ci/circleci: prerender_build" is failing
    failure status "ci/circleci: tests_browserstack" is failing
    failure status "ci/circleci: tests_local_browsers" is failing
    failure status "ci/circleci: tests_saucelabs" is failing
    pending missing required labels: target: *

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@crisbeto
Copy link
Member Author

Closing in favor of #15551.

@crisbeto crisbeto closed this Mar 20, 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 Sep 10, 2019
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 P2 The issue is important to a large percentage of users, with a workaround
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants