* build: tsconfig for editor warnings
Currently when using a code editor that uses the TypeScript language service (Webstorm / VS Code / Atom / Sublime) there will be TypeScript errors in the `.spec` files.
This is because the editor finds the `tsconfig.json` file that doesn't match the spec files. Therefore it complains about the `experimentalDecorators`.
In `angular/angular` there is a global `tsconfig` file that matches everything and is therefore fixing the editor warnings. This file is also used to compile all `.spec` files for the whole project.
We can add such a `tsconfig.json` file as well, and in the future we can use it for compiling the specs as well.
* Add docs for tsconfig files
Set up firebase functions to copy valid data to firebase storage/database
Use JasonWebToken to validate data written to firebase
Github Status change will be done in another PR
Result at: https://material2-screenshots.firebaseapp.com/3628
* Bumps the required Angular version to 4 and TypeScript to 2.1.6.
* Fixes deprecation warnings for `<template>` usages.
* Fixes any unit and e2e test failures.
* Includes the new animations module and switches any components that use animations to it.
* Fixes issues with the various test apps.
Fixes#3357.
Fixes#3336.
FIxes#3301.
* build: ship esm bundle
* Now ships a Flat / ESM bundle (similar as for Angular 4+ releases)
* In future PRs we will remove the single ES-files and can just link to the ES bundle (as in angular/angular).
* Use template strings for diagnostic
* build: show inherited members in dgeni
* Introduced a new Dgeni processor that will take care of the inherited docs for TypeScript classes.
* Cleaned up the categorizer processor and made it compatible with the `inherited-docs` processor.
* Fixes that the `docs-private-filter` processor doesn't filter the referenced members in the class docs.
This basically allows us to extend other classes in our components like in #3036
* Handle private-docs param for all docs.
* Address comments
* Address feedback
* Introduces a new directory called `util` in the gulp setup. This should make the gulp setup more clear and maintainable.
* The utility `task_helpers` no longer includes random utilities like for Firebase. Those have been moved to their own util file (similar as in `e2e/`)
* Refactors the Github Status utility because it can be useful for other things as well (e.g upcoming coverage, payload)
* Since we had a lot of TSLint issues on our tooling scripts & tasks, we should run TSLint on those as well.
* Also updates Dgeni to latest version, because it now supports TypeScript typings.
* update: add button to toggle theme in demo-app
* Adds a button to the demo-app toolbar that allows developers to quickly change between dark and light Material themes.
This is very useful when building new components or just when confirming that all components work with dark themes.
* Improve list-demo in dark-theme
* Fix stylelint
* Address comments
* Add google cloud storage
* Add screenshots to e2e test
* Renamed functions. Add types. Remove firebase, use firebase-admin
* dependencies
* Save pull request sha to firebase db
* Save travis job id
* Add function to update github commit status
* remove update status code
* Add update status
* Address comments
* Add fs-extra
* try using ES6 Promise
* .
* Fix cannot find name promise
* Add back function to save filenames to firebase
* Update comments
* Currently when running dgeni using the `gulp api` task, Dgeni will run twice.
This happens because the `dgeni/index.js` file calls `generate()` and the gulp task does that as well.
The `dgeni/index.js` file should be just responsible for exporting the dgeni package.
* Now runs TSLint also against the e2e/ directory.
* Add comments for the different tasks in the lint file.
* Refactors the screenshot e2e file to pass TSLint and also to be less nested.
* No longer publishes the `system-config-spec.ts` file in releases. Extending the glob to also remove the `-spec.ts` files.
In the future it's planned to not build spec files for releases at all..
* Properly exit karma in single-run mode when errors are recognized.
* This looks like its caused by the karma launchers, that connect to Browserstack or Saucelabs and which doesn't close the connection poperly when karma exits with an error code.
Paul Gschwendtner