Open greenkeeper[bot] opened 7 years ago
Update to this version instead 🚀
top
instead of width
after removing Renderer use (#8602) (6e865b7)Update to this version instead 🚀
"fullTemplateTypeCheck"
(#8889) (eec7c73)optionSelectionChanges
being accessed early (#8830) (c98321c)
Version 5.0.0-rc0 of @angular/material was just published.
The version 5.0.0-rc0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of @angular/material.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
cesium-cephalopodHighlights
behaviors are stable and mature enough to exit beta. Please continue to file issues that
help us eliminate more bugs from the forthcoming 5.0.0 release. Moving forward, the major
version number of Angular Material and CDK will update alongside Angular itself.
BREAKING CHANGES
mat-icon
now usesHttpClient
from@angular/common/http
instead ofHttp
from@angular/http
. Any unit tests that faked icon responses should be changed to use anHttpInterceptor
.@angular/cdk/rxjs
has been removed in favor of RxJS 5.5's lettable operators.mat-toolbar
not wrapped in amat-toolbar-row
would be rendered inside of an implicitly createdmat-toolbar-row
. As of rc0,this implicit row will no longer be created. This means that any custom application CSS that
targeted this implicitly created
mat-toolbar-row
will no longer apply. Users can re-add themat-toolbar-row
in their own templates to match the original output structure. Thisresolves a longstanding issue where
display: flex
styles were difficult to use onmat-toolbar
.@angular/cdk/accordion
CdkAccordion
and associated classes live in@angular/cdk/accordion
AccordionChild
is renamed toCdkAccordionChild
CdkAccordion
no longer has displayMode and hideToggle@Inputs
CdkAccordionItem
is now a@Directive
when
property ofmatRowDef
andcdkRowDef
has been changedfrom
(rowData, index)
to(index, rowData)
in order to matchtrackBy
.fromIso8601
method onDateAdapter
removed in favor ofdeserialize
DateAdapter
will return an invalid date instead of throwing an erroruserSelection
@Output
ofmat-calendar
has been made internal-onlyScrollDispatcher.getScrollContainers
has been renamed togetAncestorScrollContainers
tobetter match its behavior.
ScrollDispatcher.scrollableReferences
property has been renamed toscrollContainers
.ScrollDispatcher.scrollableContainsElement
method has been removed.Scrollable
class has been renamed toCdkScrollable
for consistency.@angular/cdk/collections
(
UniqueSelectionDispatcher
,UniqueSelectionDispatcherListener
, andUNIQUE_SELECTION_DISPATCHER_PROVIDER
)MATERIAL_COMPATIBILITY_MODE
,CompatibilityModule
,NoConflictStyleCompatibilityMode
,MatPrefixRejector
,MdPrefixRejector
symbols have been removed.MAT_CONNECTED_OVERLAY_SCROLL_STRATEGY
is renamed toCDK_CONNECTED_OVERLAY_SCROLL_STRATEGY
Deprecations
OverlayOrigin
->CdkOverlayOrigin
ConnectedOverlayDirective
->CdkConnectedOverlay
PortalDirective
->CdkPortal
PortalHostDirective
->CdkPortalOutlet
ObserveContent
->CdkObserveContent
@Output
names have been renamed. The old names are still available as deprecated:mat-select
onOpen
->opened
onClose
->closed
change
->selectionChange
mat-sidenav
/mat-drawer
open
->opened
close
->closed
mat-menu
close
->closed
matMenuTriggerFor
onMenuOpen
->menuOpened
onMenuClose
->menuClosed
mat-chip
onSelectionChange
->selectionChange
remove
->removed
destroy
->destroyed
mat-tab-group
selectChange
->selectedTabChange
Features
exportAs
name (#7554) (fa441bc)Bug Fixes
DateAdapter
authors to have more control ove… (#7346) (9fa075e)Performance Improvements
Code Refactoring
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: