microsoft / microsoft/TypeScript

TS 3.7: optional chaining output is introducing a local variable

Open
#34,594 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Experience Enhancement Suggestion
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

TypeScript Version: 3.7.x-dev.201xxxxx

Search Terms:
optional chaining

Code

function isTrue(something: { value: boolean} | undefined): boolean {
	return something?.value === true; 
}

Expected behavior:
Output:

"use strict";
function isTrue(something) {
    return (something === null || something === void 0 ? void 0 : something.value) === true;
}

Actual behavior:
Actual Output:

"use strict";
function isTrue(something) {
    var _a;
    return ((_a = something) === null || _a === void 0 ? void 0 : _a.value) === true;
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the provided optional-chaining example with the TypeScript 3.7 development compiler and trace the compiler's optional-chaining output path. Done means the emitted JavaScript matches the expected output without introducing the extra local variable, with coverage for this example.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.