fix(cdk/scrolling): expand type for "cdkVirtualForOf" input to work with strict null checks #17421
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
devversion
added
the
target: major
googlebot
added
the
cla: yes
devversion
added
the
P1
…ith strict null checks Currently the `cdkVirtualForOf` input accepts `null` or `undefined` as valid values. Although when using strict template input type checking (which will be supported by `ngtsc`), passing `null` or `undefined` with strict null checks enabled causes a type check failure because the type definition of the input becomes too strict with "--strictNullChecks" enabled. For extra content: by default if strict null checks are not enabled, `null` or `undefined` are assignable to _every_ type. The current type definiton of the `cdkVirtualForOf` input is incorrectly making the assumption that `null` or `undefined` are always assignable. The type of the input needs to be expanded to explicitly accept `null` or `undefined` to behave consistently regardless of the `strictNullChecks` flag. A common scenario where this breaks is the use of `cdkVirtualFor` in combination with the async pipe from `@angular/common`. This is because the async pipe returns `null` until a value has been emitted. This means that with strict null checks, the type checking will fail because `null` is not allowed. This is similar to what we did for `ngFor` in framework: angular/angular@c1bb886 Fixes angular#17411
devversion
force-pushed
the
fix/cdk-scorlling-expand-type-cdk-virtual-for-of
branch
from
bce5f38 to
1ba5d2d
Compare
mmalerba
approved these changes
Oct 16, 2019
mmalerba
added
pr: lgtm
action: merge
7 tasks
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the
cdkVirtualForOfinput acceptsnullorundefinedas valid values. Althoughwhen using strict template input type checking (which will be supported by
ngtsc), passingnullorundefinedcauses a type check failure because the type definition of the input becomestoo explicit with "--strictNullChecks" enabled.
For extra content: by default if strict null checks are not enabled,
nullorundefinedare assignable to every type. The current type definiton of the
cdkVirtualForOfinputis incorrectly making the assumption that
nullorundefinedare always assignable.The type of the input needs to be expanded to explicitly accept
nullorundefinedto behave consistently regardless of thestrictNullChecksflag.This is similar to what we did for
ngForin framework: angular/angular@c1bb886Fixes #17411