microsoft / microsoft/TypeScript
Regression: incorrect return type when disabled strictNullChecks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
🔎 Search Terms
"ts7011", "strictnullchecks"
🕗 Version & Regression Information
- This changed between versions 5.6.3 and 5.7.0-beta (also in 5.7.0-dev.20241010)
When disabled strictNullChecks in tsconfig.json error TS7011: Function expression, which lacks return-type annotation, implicitly has an T return type
⏯ Playground Link
💻 Code
declare function wildcardToRegExp(s: string): RegExp | null;
const rules = ['a', 'b'].flatMap(rule => wildcardToRegExp(rule) || []); // if flatMap<RegExp> - no error
🙁 Actual behavior
TS7011: Function expression, which lacks return-type annotation, implicitly has an 'RegExp | any[]' return type.
🙂 Expected behavior
No error
Additional information about the issue
No response
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 linked Playground case with TypeScript 5.7 and the shown tsconfig settings, then compare it with 5.6.3. The change is complete when the flatMap callback no longer produces TS7011 with strictNullChecks disabled while the reported behavior remains correct.
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
- 42/100