This adds bazel test rules for everything under cdk/ and sets CircleCI Overlay tests don't work because there's not yet a way to pass through flags to the browser. These issues will be addressed in a follow-up PR.
Bumps to the latest minor version of Angular now that a compilation error, that was blocking us previously, has been resolved. Also fixes a couple of AoT errors in the demo app.
* feat(datepicker): @Output of year and month selected in multiyear/year
views
* address @mmalerba's comments
* address comments
* add types to some outputs
* fix wrong parameter type
* restore accidentally removed object
* example and docs text
* change emitted values to objects instead of just numbers
* change datepicker.md and switch back tslint configs
* fix nit
* Remove changes in demo app
This fixes an issue where requests for icons in a particular set made
while that set is being fetched result in the set being parsed into an
SVGElement multiple times. It occured because, while the same pending http
request was used for each icon, each icon added their own `map` onto
that request, will every `map` resulting in a (potentially expensive) parse. This change sets the cached icon earlier and checks it later.
Previously in `RxJS`, operators were part of the `Rx.Observable` namespace, but now since those will be imported separately from the `rxjs/operators` path, the UMD module name mapping needs to be updated to `Rx.operators` (https://unpkg.com/rxjs@5.5.2/bundles/Rx.js)
Fixes#8530
Bumps the required RxJS version to 5.5.0 and gets rid of our RxChain in favor of using the lettable Rx operators. Refactors all the usages and updates the configs.
Fixes#7275.
With (DefinitelyTyped #21004) the typings for @gulp-utils are declaring `chalk` as dependency of the types. This causes a conflict with the types from chalk and gulp fails everywhere in the CI. (https://github.com/DefinitelyTyped/DefinitelyTyped/issues/21004)
A possible solution would be locking the version of the gulp-util types to the working version `3.0.31`.
As `gulp-utils` is only used in one place right now, we are just remove the `gulp-utils` import and just use `console.log` as everywhere else.
* No longer creates the coverage reports inside of Browserstack. The reports can be generated inside of Chrome Headless that doesn't run remotely on BrowserStack or Saucelabs.
* Now re-runs the given deploy mode a second time if failed the first time. This ensure that deployment works fine most of the time and should also avoid conflicts between different Travis CI jobs that are deplyoing at the same time.
Before this change, all of `@angular/material` was bundled into a
single, flat JS file.
After this change, each top-level component (i.e., each directory under
`src/lib`) will be have its own JS file (and d.ts and metadata.json).
The benefit of this change is that current versions of webpack will be
able to do a much better job of only including the code an app is using.
It also allows (but does not require) people to explicitly import from specific components,
e.g.
```
import {MdButtonModule} from '@angular/material/button';
``
For development _within Angular Material itself_ we have to use these
deeper imports because the root `@angular/material` doesn't exist until
we build the relase package.
Additionally, this PR adds a `tsconfig.json` for each dir under `src/`
with the correct path mappings for that directory, so that IDEs will
correctly generate imports.
Closure Compiler CI check is also disabled by this PR; it cannot work
with the new package structure until a release with
https://github.com/google/closure-compiler/pull/2600 is made available.
Currently the custom TSLint rules of the repository had to be pushed as JavaScript files because TSLint was only able to run them as JavaScript files.
Recently with TSLint 5.7.0 (https://github.com/palantir/tslint/commit/90dd3f472199c68662eaecc47663969cb8ea6ed1), custom rules can be also loaded directly as TypeScript files in combination with ts-node.
For every Pull Request, a job that runs the Google Closure Compiler against the demo-app will be started. In the past Closure Compiler wasn't able to properly handle CommonJS packages from the node modules.
Now the Google Closure Compiler will be reconfigured to properly handle CommonJS packages (meaning that RxJS no longer needs to be built manually)
* feat: update to Angular 4.3
* Bumps the Angular requirement to 4.3. This is also a prerequisite to the Angular 5 update since we encountered the same errors there.
* Refactors the sidenav not to use a `Promise.resolve` for toggling the initial animation, because it was making it impossible to flush the animations in unit tests. The new simplified approach uses a property to pass the animation state.
* Fixes the nested menu test failures.
* Fixes a "changed after checked" error in the autocomplete demo app.
Relates to #6454.
* fix: e2e failures
A few custom TSLint rules already accept an option array that can be used to whitelist specific files. These whitelists are based on normal Regular Expressions which do not work very well for path matching.
This commit changes the existing whitelists to use minimatch, which is a package that allows matching strings/paths against globs. For rules like `requireLicenseBanner` where the whitelist is hardcoded right now, the whitelist has been introduced as well.
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.
* Fixes the stylelint deprecation warning
* Fixes that stylelint lints the compiled bundles from `dist/` folders of the `dashboard` or `screenshot` app
* Updates the package-lock with NPM@5.1
Andrew Seguin