fix(module:input): fix type error

[create-share]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
#282

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

[coveralls]

Coverage remained the same at 40.722% when pulling e9c415b on deart1mer:fix-type-error-of-autosize into 46ae81a on NG-ZORRO:master.

[vthinkxie]

duplicated #271 and it is not a bug but a hack.

[create-share]

@vthinkxie Got it.
But I think it's hard to accept an error when running npm run start to develop.
It could be handled like disabled attribute in form element. If it it an attribute, no matter what the value is true. If it is set to a type of boolean or AutoSizeType as an input value, match the boolean | AutoSizeType type.

Such like this:

  set nzAutosize(value: string | boolean | AutoSizeType) {
    if (typeof value === 'string') {
      this._autosize = true;
    } else {
      this._autosize = <boolean | AutoSizeType>value;
    }

    if (this._autosize) {
      this._render.setAttribute(this.nativeElement, 'autosize', '');
    } else {
      this._render.removeAttribute(this.nativeElement, 'autosize');
    }
  }

Is that a good way?

[vthinkxie]

@deart1mer yes, but it is strange that there is no error when I run npm run start, and CI is ok.
You can update your pr as your newest code if it can fix your environment.

[create-share]

@vthinkxie OK :-)

[coveralls]

Coverage remained the same at 40.722% when pulling 92fe1c9 on deart1mer:fix-type-error-of-autosize into 46ae81a on NG-ZORRO:master.

[standbyme]

😄 I thought I was the only one who ran into this bug before this PR....

[LinboLen]

btw, I think autosize is ambiguity.