microsoft / microsoft/TypeScript
No error from noUnusedLocals option on ambient local variable in module file
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.20200116
Search Terms:
Code
export { }
declare const Array: void;
Expected behavior:
error
Actual behavior:
pass
Playground Link: https://www.typescriptlang.org/play/index.html?noUnusedLocals=true&ts=3.8.0-dev.20200116&ssl=1&ssc=1&pln=3&pc=27#code/KYDwDg9gTgLgBAbzgXwFCoCbAMYBsCGUwc2EAdgM7wCCUU+AngFxwBuEAlhgNxA
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 supplied TypeScript code and Playground link, using the reported 3.7.x-dev.20200116 or 3.8.0-dev.20200116 settings to reproduce the difference between expected and actual behavior. Trace how noUnusedLocals handles the ambient local declaration in a module file, then verify that the example reports the expected error without changing unrelated cases.
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
- Clearly specified
- Newbie friendliness
- 45/100