Closed greenkeeper[bot] closed 6 years ago
After pinning to 2.0.0-beta.7 your tests are passing again. Downgrade this dependency 📌.
Your tests are still failing with this version. Compare the changes 🚨
md-optgroup
Overlay
moved to @angular/cdk
MdSelectionList
md-input-container
renamed to md-form-field
(while still being backwards compatible)OnPush
change detection (dialog being the exception)EmbeddedViewRef
when attaching a TemplatePortal
MdSidenav
has been split into MdSidenav
and MdDrawer
. The MdSidenav
is now meant to be@angular/cdk
are now scoped to a specific sub-package. For example, if youimport {LiveAnnouncer, Overlay, Directionality} from '@angular/cdk';
You will now need to write:
import {LiveAnnouncer} from '@angular/cdk/a11y';
import {Directionality} from '@angular/cdk/bidi';
import {Overlay} from '@angular/cdk/overlay';
This helps ensure you're only pulling in the pieces of the cdk being used as well as providing more
context about what an imported symbol is being used for.
The current set of public @angular/cdk
subpackages are:
a11y, bidi, coercion, collections, keycodes, observers, overlay, platform, portal, rxjs,
scrolling, table.
If you are using SystemJS, each package you use must be added to the SystemJS configuration.
Overlay
code has been moved from @angular/material
to @angular/cdk
. The symbols are@angular/material
, but these re-exports will be removed in acdkScrollable
, ScrollDispatcher
, and ViewportRuler
have been moved from overlay into itsscrolling
subpackage in @angular/cdk
.200px
by default (similar to native input elements). Themat-form-field
css class.mat-input-container-
to mat-form-field-
.md-prefix
and md-suffix
are now mdPrefix
and mdSuffix
.TemplatePortal
now requires a generic type (C) to align with TemplateRef
.any
.EmbeddedViewRef<C>
instead of anMap
.ObserveContentModule
has been renamed to ObserversModule
PositionStrategy
now has an attach
method and no longer passes the overlayapply
.mdDatepickerToggle
is now an element <md-datepicker-toggle>
with a for
MdDatepicker
instanceNativeDateAdapter
will now use Angular's LOCALE_ID instead of the browser'smat-sidenav-
to mat-drawer-
0
and 1000
hues have been removed from the mat-gray
paletteselectable
property of the md-chip-list
hasmd-chip
to maintain consistency with the newremovable
option.If you used the following code,
<md-chip-list [selectable]="selectable">
<md-chip>My Chip</md-chip>
</md-chip-list>
you should switch it to
<md-chip-list>
<md-chip [selectable]="selectable">My Chip</md-chip>
</md-chip-list>
@Directive
selectors are deprecated in favor of the camelCase equivalent. TheOld | New |
---|---|
md-line | mdLine |
md-tab-link | mdTabLink |
md-tab-label | mdTabLabel |
md-card-avatar | mdCardAvatar |
md-input-container
has been renamed to md-form-field
. The old selector will be removed in amd-select
a child of md-form-field
@Input()
is now also prefixed. For example,cdkConnectedOverlay
now has inputs forcdkConnectedOverlayOrigin
, cdkConnectedOverlayPositions
, etc. The class members themselves arecdkPortalHost
, cdkConnectedOverlay
, mdTooltip
, mdTextareaAutosize
, and mdMenuTriggerFor
.MdCoreModule
is deprecated and will be removed in a subsequent release now that most of its@angular/cdk
MaterialModule
is deprecated and will be removed in a subsequent release (seedir
and changes
readonly (#5645) (8c13325)Your tests are still failing with this version. Compare the changes 🚨
@angular/material
component is now bundled into its own javascript file. This will allow@angular/cdk
with Material Design flavors in@angular/material
.MaterialModule
has been removed. (cf1ece0) (#6803)MdCoreModule
has been removed. Most of its functionality has been moved to @angular/cdk
overFocusOriginMonitor
has been renamed to FocusMonitor
and moved to @angular/cdk
.select
and deselect
have been removed in favor of a singleonSelectionChange
output.themeClass
property has been removed. To add a class to theoverlayContainer.getContainerElement().classList.add('my-theme-class');
getISODateString
has been renamed to toIso8601
and a new methodfromIso8601
has been added.In earlier betas, we've had a compatibility mode that allowed people to use either "md" or "mat"
as the selector for Angular Material components. This was created so that these components could
live side-by-side with AngularJS Material without CSS from
the two libraries colliding.
For beta.11, we've made the decision to deprecate the "md" prefix completely and use "mat" moving
forward. This affects all class names, properties, inputs, outputs, and selectors (CSS classes were
changed back in February). The "md" prefixes will be removed in the next beta release.
You can automatically update your projects with the angular-material-prefix-updater tool.
Check out the tool's page for instructions on how to run.
We like the "md" prefix too! We added compatibility mode in order to keep "md" around, but over
time we found that there were too many downsides to continue supporting both prefixes at the same
time:
NgModule
.We explored this option early on (before creating compatibility mode). We found that changing the
library's styles such that they wouldn't affect the Angular Material components would increase
the specificity. This would have been a significant breaking change, as it would have potentially
broken countless custom styles that relied on a particular specificity working.
mat
exportAs and class aliases (#7106) (a96b545)preserveWhitespaces: false
to all components (#7115) (2b0315d)Your tests are still failing with this version. Compare the changes 🚨
mat-select
is now used inside mat-form-field
. This makes all of the existing form-field features available with mat-select
, including hints, errors, prefixes, and suffixes. This also ensures that mat-select
and matInput
have a consistent presentation.<mat-form-field>
<mat-select placeholder="State">
<mat-option *ngFor="let state of states" [value]="state">{{ state }}</mat-option>
</mat-select>
</mat-form-field>
ScrollDispatcher.scrolled
subscription would react both on scroll events and on window resize events. Now it only reacts to scroll events. To react to resize events, subscribe to the ViewportRuler.change()
stream.UniqueSelectionDispatcher
, UniqueSelectionDispatcherListener
and UNIQUE_SELECTION_DISPATCHER_PROVIDER
are no longerisFocusTrapEnabled
is now properly marked internal.OverlayRef.getState
method has been renamed to OverlayRef.getConfig
.defaultErrorStateMatcher
has been replaced by ErrorStateMatcher
. For more info, see the input docs.mat-tab-label-active
class to active nav tab labels (#7508) (00e9338)
Version 2.0.0-beta.8 of @angular/material just got published.
This version is covered by your current version range and after updating it in your project the build failed.
@angular/material is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/flightwatching/svg-animator/builds/250859121?utm_source=github_status&utm_medium=notification)Release Notes
plasma-abacusHighlights
@angular/cdk
(component dev kit)! This package containsgeneral building blocks for UI components decoupled from the visuals of Material Design. In the
initial release, code from Angular Material's
core/
have been moved fora11y/
,bidi/
,coercion/
,observe-content/
,platform/
,portal/
. The@angular/material
package nowre-exports these symbols, marked as deprecated. The re-exports will be removed in a subsequent
release.
<cdk-table>
(the core) and the<md-table>
(with Material Design styles). See the documentation on material.angular.io for moreinformation.
<md-paginator>
and<md-sort-header>
components, which can be used eitherwith
<md-table>
or any other table.@angular/material
and@angular/cdk
are now strict null compliant.Breaking changes
@angular/material
now depends on@angular/cdk
as a peer dependency.| null
or| undefined
for strict null compatibility. Ifyour application uses strict null checks, you may have to update the types in your app to match up
with the more accurate types coming from Angular Material.
Observable
. If your appdepended on these operators being added by Angular Material, you will need to import them
explicitly.
Bug Fixes
Features
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: