-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
refactor(multiple): switch to non-deprecated MDC list styles #22504
Conversation
Caretaker note: in the process of migrating the styles for |
9fbe441
to
8fb3c36
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. One minor comment/question.
@crisbeto is this available in canary now? |
It's not available in canary yet. It's waiting for material-components/material-components-web#7021. |
8fb3c36
to
7c612b7
Compare
Unblocking this since the necessary changes are in the canary branch now. |
7c612b7
to
e957449
Compare
97faee6
to
89dc94a
Compare
FYI, I had to lock us to a specific canary version, because having the caret in the version caused yarn to install an older canary version of MDC for some reason. I've locked us to the current latest canary. |
Our MDC version requirement currently uses a caret with the intention of allowing any version after the specified canary. This isn't actually how npm works and it can end up installing an earlier version. The version isn't technically valid semver, causing the package manager to sort the versions alphabetically and to pick the last one. This behavior threw me off when rebasing angular#22504 yesterday, because it ended up installing a version that was too old. These changes lock us to a specific version.
Our MDC version requirement currently uses a caret with the intention of allowing any version after the specified canary. This isn't actually how npm works and it can end up installing an earlier version. The version isn't technically valid semver, causing the package manager to sort the versions alphabetically and to pick the last one. This behavior threw me off when rebasing angular#22504 yesterday, because it ended up installing a version that was too old. These changes lock us to a specific version.
Our MDC version requirement currently uses a caret with the intention of allowing any version after the specified canary. This isn't actually how npm works and it can end up installing an earlier version. The version isn't technically valid semver, causing the package manager to sort the versions alphabetically and to pick the last one. This behavior threw me off when rebasing #22504 yesterday, because it ended up installing a version that was too old. These changes lock us to a specific version.
89dc94a
to
abf8f52
Compare
803ef9a
to
24a3d6c
Compare
Switches the components in `mdc-autocomplete`, `mdc-core`, `mdc-menu` and `mdc-select` to the non-deprecated MDC list styles.
24a3d6c
to
8389383
Compare
Switches the components in `mdc-autocomplete`, `mdc-core`, `mdc-menu` and `mdc-select` to the non-deprecated MDC list styles. (cherry picked from commit f960a7a)
Switches the components in `mdc-autocomplete`, `mdc-core`, `mdc-menu` and `mdc-select` to the non-deprecated MDC list styles. (cherry picked from commit f960a7a)
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. |
Switches the components in
mdc-autocomplete
,mdc-core
,mdc-menu
andmdc-select
to the non-deprecated MDC list styles.Note for reviewer: merging this is currently blocked, because it depends on one change that isn't in the latest canary version. Once the change is released, I'll bump the version and unblock merging. The code can still be reviewed.