m67hoff / material2-sample Goto Github PK
View Code? Open in Web Editor NEW:no_entry: DEPRECATED ! Simple Angular Material 2 Sample with always actual dependencies. Built with angular-cli
:no_entry: DEPRECATED ! Simple Angular Material 2 Sample with always actual dependencies. Built with angular-cli
Branch | Build failing 🚨 |
---|---|
Dependency | @angular/cdk |
Current Version | 2.0.0-beta.9 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
@angular/cdk 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 💪
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)There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | karma |
Current Version | 1.7.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As karma is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
The new version differs by 3 commits.
ee40570
chore: release v1.7.1
66b08e6
chore: update contributors
ea32194
feat(deps): add support for node@8
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.travis.yml
If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.
Greenkeeper has checked the engines
key in any package.json
file, the .nvmrc
file, and the .travis.yml
file, if present.
engines
was only updated if it defined a single version, not a range..nvmrc
was updated to Node.js 10.travis.yml
was only changed if there was a root-level node_js
that didn’t already include Node.js 10, such as node
or lts/*
. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.For many simpler .travis.yml
configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | @angular/material |
Current Version | 2.0.0-beta.7 |
Type | dependency |
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 💪
@angular/cdk
(component dev kit)! This package containscore/
have been moved for a11y/
, bidi/
,coercion/
, observe-content/
, platform/
, portal/
. The @angular/material
package now<cdk-table>
(the core) and the<md-table>
(with Material Design styles). See the documentation on material.angular.io for more<md-paginator>
and <md-sort-header>
components, which can be used either<md-table>
or any other table.@angular/material
and @angular/cdk
are now strict null compliant.@angular/material
now depends on @angular/cdk
as a peer dependency.| null
or | undefined
for strict null compatibility. IfObservable
. If your appThere is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | ts-node |
Current Version | 3.2.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As ts-node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Fixed
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.
Since we did not receive a CI status on the greenkeeper/initial
branch, we assume that you still need to configure it.
If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/
.
We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
Branch | Build failing 🚨 |
---|---|
Dependency | @types/node |
Current Version | 8.0.15 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.
Since we did not receive a CI status on the greenkeeper/initial
branch, we assume that you still need to configure it.
If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/
.
We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.