The GitHub code owners feature does not work properly right now because the different paths/globs to the folders (like the `input`) are not matching at all.
This is because the paths are not absolute nor relative paths but still include a directory name. This does not work properly and can be confirmed by playing with the `.gitignore` (which has the same pattern matching)
* The pure annotations are no longer added to ES5 bundles of Angular Material or the CDK. The pure annotations should be added by the new build optimizer which is part of the CLI.
* Adds peer dependencies for the CDK and Material to the examples package. This ensures that the API that is used in the examples is always compatible with the current installed version of the CDK or Material.
Updates tslint to 5.5.0 and resolves some errors that weren't being caught before. This version also has the advantage of printing out the full stack trace if one of the rules throws an error.
* The closure script now detects the CDK entry points from the filesystem. This is important to avoid hard-coding the CDK entry points multiple times in the project.
Recently the version placeholders had been replaced with hardcoded versions because it was necessary to be able to release the CDK.
But now the version placeholders are replaced in every file and therefore they can be used instead of the hardcoded values.
* docs: individual cdk entry points for systemjs
* Updates the SystemJS guide section to show that the individual CDK entry points need to be mapped manually.
* Address feedback
Currently the pseudo checkbox both inherits its colors via CSS and has a `color` input. This means that if we wanted to the keep it in sync with its parent component (e.g. a multi-select), we'd have to add some boilerplate that listens to changes, goes through and updates all of the checkboxes, and triggers change detection while avoiding the "changed after check" assertions.
Since the component is meant to be really lean and to inherit its colors from the parent, these changes remove the `color` input altogether in order to reduce the complexity and be clearer regarding the intended usage.
Since the same is true for the `md-option` component, I've removed the `md-options.{{ palette }}` selectors as well.
Fixes#6079.
Adds a custom tslint rule that ensures that we've added all of the necessary external modules to the Rollup config. This is helpful, because forgetting to add a module will log a warning, but it won't break the build necessarily, which is why we occasionally need PRs like #5930.
* fix(datepicker): refactor toggle to fix theming and allow it to be
combined with button directives
* update usages of datepicker toggle
* change to suggested API
* fix new uses of mdDatepickerToggle after rebase
* If a developer sets an initial value for the slide-toggle the NgControl of the slide-toggle can turn dirty. The slide-toggle should only turn dirty if the value changed after initialization. This adds a test to confirm that this is not the case.
* refactor(sidenav): switch to the angular animations API
Switches the sidenav to use the `@angular/animations` API. This saves us a lot of code that was involved in orchestrating the various animations, in addition to making it easier to follow. It also makes it possible for the consumer to disable the animations by using the `NoopAnimationsModule`.
* chore: remove redundant annotations
* fix: focus restoration issue in IE
* chore: linting error
* chore: put back the toggle animation promises
* fix: avoid initial animation
* fix: sidenav not showing when animation starts
* chore: update e2e tests
Adds an extra null check when trimming the checkbox `textContent`. This avoids issues in Universal where the `textContent` will be undefined.
Fixes#5453.
* fix(expansion-panel): toggle not being updated when set programmatically
Fixes the toggle arrow not being flipped when the `expanded` is set programmatically, in addition to the `hideToggle` input not working either. This is a regression from #5549 and is a consequence of the fact that the panel header reaches into the panel to determine what to do with the arrow.
Fixes#5623.
* chore: add a couple of unit tests for the fixes
* Adds a `pointer-cursor` to the chip remove button to indicate that it's clickable.
* Adds a transition to the focused chip `box-shadow` to make it less harsh.
* Breaks up a long line that was exceeding our character limit.
Fixes issue in the grid list that was causing it to set invalid styles when it is rendered on the server-side. It's because the browser converts the camelCased styles to dash-case automatically, but that doesn't happen on the server.
Fixes#6048.
* Cleanup harsh colors for selected button toggle
- Light theme: black -> black-54
- Dark theme: white -> white-70
* Make the slider min thumb less harsh in light theme
- Light theme: black -> black-87
- Dark theme: white -> white
* Use default text color for expansion panel
* fix(slide-toggle): invalid model change event (#4140)" (#4218)
While initially looking into #4124, there were a few more issues inside of the slide-toggle.
* ngModelChange event is dispatched at initialization.
* Checked state isn't synchronized when state changes through drag. New state after dragging got overwritten by click event on label.
* Removes unnecessary logic inside of `change` listener. Change event doesn't fire if underlying checkbox is disabled.
Fixes#4124.
* Cast NgModel value to a boolean
* Properly mark component for check
* In releases there will be a constant called `VERSION` that holds the current version of the installed package (material or cdk)
* This is similar as for every @angular package like core, forms, compiler.
Paul Gschwendtner