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.

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

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

Closed
wants to merge 2 commits into from

Conversation

Splaktar
Copy link
Member

This adds 731b80d on top of PR #17392 to update to Angular 9.0.0-next.11 and CLI 9.0.0-next.12 while keeping "fullTemplateTypeCheck": true.

So far this includes many fixes, but it is not yet done as quite a few more errors remain to resolve.

- 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 added the refactoring This issue is related to a refactoring label Oct 18, 2019
@Splaktar Splaktar added this to the 9.0.0 milestone Oct 18, 2019
@Splaktar Splaktar self-assigned this Oct 18, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 18, 2019
@Splaktar
Copy link
Member Author

We've decided to switch to "fullTemplateTypeCheck": false until we can make some of our typings less strict. I'm leaving this WIP PR here for now as a reference and may return to it in the future.

@Splaktar Splaktar changed the title refactor: update to Angular 9.0.0-next.11 and resolve template errors refactor: attempt to resolve @Input template type errors Oct 21, 2019
@Splaktar Splaktar removed this from the 9.0.0 milestone Oct 22, 2019
@mmalerba
Copy link
Contributor

mmalerba commented Mar 6, 2020

Closing for now, we can re-open in the future if we want to revisit this

@mmalerba mmalerba closed this Mar 6, 2020
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes PR author has agreed to Google's Contributor License Agreement refactoring This issue is related to a refactoring
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants