This allows us to cherry-pick @kara's static query updates from the
`ivy-2019` branch.
This change includes:
* Adding missing dependencies for various Angular subpackages
* Add umd assets where they are now necessary
* Configure bazel to target ES5 output as a workaround for https://github.com/angular/angular/issues/29107
* Updates most npm dependencies to the @npm// workspace
* Updates general workspace setup, RBE config, ngcontainer
* Update to rxjs 6.4.0 (building from source no longer needed)
* Added rxjs_shims for ts_web_test and ts_devserver targets
* Removed index.bzl and angular_material_setup_workspace (not needed anymore since material won't be built from source)
* Use browser_repositories() from @npm_bazel_karma which have pinned browsers that work on all platforms
* Change dgeni processor functions from arrow function to `function` to
work around `@npm//di` not supporting arrow functions
Co-authored-by: Greg Magolan <gmagolan@gmail.com>
* SystemJS is responsible for loading `tslib` and `moment` as registered AMD modules. This means that we don't need to include them in Karma as well. Currently the browsers fetches Moment and tslib twice and also runs it without having any necessary effect.
* build: increase saucelabs connect timeout
At some point we went down from a 2min wait timeout to 30seconds because we re-ran the startup script if something failed. Since re-running didn't really help and we removed it, we should move the timeout back to a longer period.
e.g. see: https://circleci.com/gh/angular/material2/25254 where it successfully acquired a tunnel, but just didn't have enough time to actually establish it.
* Switch to rewritten saucelabs version
* Update to latest saucelabs launcher version
* The slide toggle tests no longer import the test gesture config from `../slider/`
* The datepicker month constants from `@angular/material/core` have been moved to `lib/testing`. The old export from `core` will be kept for backwards compatibility until V8
Restructures the demo-app by no longer mixing up the `demo-app` name.
Currently the `demo-app` consists of two parts:
* The demo-app
* And the accessibility demos
As you can tell above, this is pretty much confusing because it's
technically just consisting of:
* Accessibility demos
* Library demos
This change cleans up the naming and makes sure that the modules are
structured in a best-practice way.
It's odd to have the `DemoAppModule` (*not the root module*) that
includes all library demos as a folder next to the actual demo
components.
This makes it extremely hard to convert the demo-app to Bazel because
we cannot target all `.ts` files through `glob` because it only matches
files inside of the same folder (or Bazel package).
In order to make it easy to run the demo-app with Bazel, and to just
clean it up, the folder structure should be as followed:
```
src/a11y-demo/
| ...
src/dev-app/
| ${DEMO_COMPONENT}
| ...
| BUILD.bazel
| index.html
| BUILD.bazel
```
* Currently it can happen that our tunnel identifier conflicts with other tunnel identifiers from other Angular projects. A few PRs reported that their tunnel couldn't be re-opened because it was already used and closed successfully.
* Since we going to move from Travis to CircleCI we don't want to use the dashboard anymore. Since nobody has been
looking at the dashboard frequently, it just makes things more complicated and additionally we will be using
the Github robot in order to keep track of size changes.
* No longer runs e2e tests inside of Saucelabs because Chrome is also installed on Travis CI and we should keep Saucelabs available for other browsers that don't run inside of Dockers or Travis.
* No longer just runs the tests against the first browser of a test platform (travis, saucelabs, browserstack)
* Stability is more valuable than speed (runs sequentially on CI now)
* Update Saucelabs Connect
* Remove unused spec reporter
* Update from Edge 14 to Edge 17
* Fix pixel deviations in Edge 17
* A `index.ts` file for the Material package has been added at some point. To be consistent, we switch away from `public-api.ts` to `index.ts` for the output of the individual packages.
* feat(virtual-scroll): fixed size virtual scroll (#9316)
* feat(virtual-scroll): fixed size virtual scroll
* address some comments
* change VirtualScrollStrategy interface a bit
* address some more comments
* fix lint & build
* chore: move virtual-scroll to cdk-experimental (#9974)
* virtual-scroll: simplify scroll listener logic (#10102)
* virtual-scroll: only move views that need to be moved (#10099)
* virtual-scroll: only move views that need to be moved
* address comments
* virtual-scroll: switch `throttleTime` to `sampleTime` (#10179)
* virtual-scroll: switch throttleTime to sampleTime
* add comment
* virtual-scroll: allow user to pass `Observable<T[]>` (#10158)
* virtual-scroll: rename `Range` to `ListRange` to avoid confusion with native `Range` (#10220)
* virtual-scroll: add autosize scroll strategy (#10219)
* rename fixed size virtual scroll directive
* add autosize virtual scroll strategy
* add item size estimator class
* add logic for jumping rendered content based on scroll position
* address comments
* virtual-scroll: add `onContentRendered` hook to `VirtualScrollStrategy` (#10290)
* virtual-scroll: add `onContentRendered` hook to `VirtualScrollStrategy`
* address comemnts
* virtual-scroll: add incremental scroll logic in `AutosizeVirtualScrollStrategy` (#10504)
* virtual-scroll: add incremental scroll logic in `AutosizeVirtualScrollStrategy`.
This still has a couple issues that need to be ironed out and it doesn't
have the code for correcting the error between the predicted and actual
scroll position. (See various TODOs for additional things that need
work).
* fix lint
* address comments
* address comments
* fix bazel
* fix devapp
* fix lint
* cleanup
* virtual-scroll: rewrite offset in terms of "to-top" and fix a bug where items were removed too soon (#10986)
* rewrite offsets to the end of the rendered content as offsets to the
start
* add some more autosize demos for testing
* make sure not to remove too many items
* address comments
* virtual-scroll: address amcdnl's feedback (#10988)
* rewrite offsets to the end of the rendered content as offsets to the
start
* add some more autosize demos for testing
* make sure not to remove too many items
* virtual-scroll: address amcdnl's feedback
* virtual-scroll: fix updating when data changes and add trackBy demos (#11085)
* virtual-scroll: add logic to correct the scroll position as user move… (#11137)
* virtual-scroll: add logic to correct the scroll position as user moves toward the top
* address comments
* fix(scrolling): adds right to fix pushed content (#11192)
* fix(scrolling): adds right to fix pushed content
* chore: address feedback
* chore: address pr feedback
* virtual-scroll: add tests for fixed size items (#11255)
* virtual-scroll: add tests for fixed size items
* address comments
* fix bug in fixed size strategy
* fix bazel build
* virtual-scroll: add tests for `cdkVirtualFor` logic (#11275)
* merge fixed size test components into one
* add tests for cdkVirtualFor logic
* allow undefined to be explicitly passed as trackBy
* fix bazel build
* address comments
* add some basic tests (#11295)
* fix lint
* virtual-scroll: add e2e tests for autosize scroll strategy (#11345)
* set up virtual scroll page in e2e app
* add gulp task for e2e:watch
* add e2e tests for autosize
* address comments
* address comments
* fix lint and tests
* fix bad rebase
* fix(scrolling): scrollbar jump when data change on scroll (#11193)
* fix(scrolling): data change not updating size
* chore: remove todo
* chore: more performant fix for jump
* move autofill to cdk
* move textarea autosize into cdk
* fix bazel build
* rename input to text-field
* set resize back to none for autosize in input css
* fix tsconfig
Currently if something throws an error right after Karma has initialized, the log will look something like the following:
```
HeadlessChrome 0.0.0 (Windows 10 0.0.0) ERROR
{
"originalErr": {},
"__zone_symbol__currentTask": {
"type": "microTask",
"state": "notScheduled",
"source": "Promise.then",
"zone": "<root>",
"cancelFn": null,
"runCount": 0
}
}
```
These changes log out the stack trace explicitly so we have some more info to work with if it happens.
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.
* Adds an initial implementation of the new `MatBottomSheet` service that allows users to display component-based or template-based bottom sheets.
* Sets up the various boilerplate and infrastructure necessary for a new component.
Note: this is an initial implementation that has the necessary functionality, styles and accessibility. More docs, examples and touch gestures will be added in a follow-up.
In order to align with the `angular/angular` setup, we also remove the temporary Chrome Headless Sandbox workaround in favor of faster Travis CI containers. To be able to still use headless chrome, we specify the `no-sandbox` flag.
Reference https://github.com/angular/angular/pull/21641
Jeremy Elbourn