microsoft / microsoft/TypeScript
strictPropertyInitialization option doesn't work with computed properties
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
TypeScript Version: 3.7.x-dev.20200118
Search Terms:
Code
const sym = Symbol();
class A {
a: 0;
['b']: 0;
[sym]: 0;
[Symbol.toPrimitive]: 0;
}
Expected behavior:
Error with all properties.
Actual behavior:
Error only with 'a'.
Playground Link: https://www.typescriptlang.org/play/index.html?ts=3.8.0-dev.20200118&ssl=1&ssc=1&pln=7&pc=2#code/MYewdgzgLgBBCeBbGBeGBlJAjEAbAFAJQDcAUMLgIYQQwCCMA3qTKzJQFwwAMZbMAbQDkWIQF0uvFmwEJEEnnxmZEOXADooIAAoAnAJaJ9UfQDcApgqkBfIA
Related Issues:
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 with the strictPropertyInitialization check using the supplied class example and Playground link. Trace how named and computed properties are handled, then add coverage for the reported expected behavior and verify that diagnostics include all properties.
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