microsoft / microsoft/TypeScript
`null!` still has the type `null` outside of `strictNulllChecks`
Open
Nobody has claimed this yet.
Bug
Domain: check: Control Flow
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
// @strictNullChecks: false
let x = null!.yadda;
// ~~~~~ Object is possibly 'null'.
Hmm
// @strictNullChecks: false
let x = null!!!!.yadda;
// ~~~~~~~~ Object is possibly 'null'.
Is this working as intended @ahejlsberg?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the supplied examples with strictNullChecks disabled and compare the diagnostics for null!.yadda and null!!!!.yadda. Determine from the issue whether these expressions should avoid the null diagnostic; the issue names no source file or test, so the relevant compiler entry point and completion test are not specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100