Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

refactor: attempt to resolve @Input template type errors #17441

Closed
wants to merge 2 commits into from
Closed

refactor: attempt to resolve @Input template type errors #17441

wants to merge 2 commits into from

Commits on Oct 18, 2019

  1. refactor: enable Ivy and fix template type checking issues 

    - enable Ivy and fix template type checking in Bazel
  - for libraries, examples, dev-app, CI
  - add `postinstall` task for `ivy-ngcc` and configure it for our SystemJS setup
- pin to Angular `9.0.0-next.10` for this PR
  - Angular `9.0.0-next.11` brings in a lot of new template type checking errors
- fix buggy show bounding box checkbox in connected-overlay-demo
- fix stylelint to work with WebStorm plugin
- restrict NodeJS version to 10.x
  - We can't go to NodeJS 12.x without dropping or upgrading Gulp to 4.x
- export `ProgressBarMode` type from `mdc-progress-bar` and `mat-progress-bar`
- export `MatDrawerMode` type from `mat-drawer`
- Add `| null` to `mat-tab-body`'s `@Input() origin: number;`

Fixes #16606. Closes #16373.
    @Splaktar
    Splaktar committed Oct 18, 2019
    Configuration menu
    Copy the full SHA
    a4546e5 View commit details
    Browse the repository at this point in the history

  2. refactor: update to Angular 9.0.0-next.11 and resolve template errors

    @Splaktar
    Splaktar committed Oct 18, 2019
    Configuration menu
    Copy the full SHA
    731b80d View commit details
    Browse the repository at this point in the history