microsoft / microsoft/TypeScript

Improve error when parameter is missing a name

Open
#22,203 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Domain: Error Messages Help Wanted Suggestion
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

TypeScript Version: 2.8.0-dev.20180227
Code

declare class C {
    f({ x?: number }): void;
    g(): void;
}

Expected behavior:

At the ?, property in destructuring may not be marked optional.

Actual behavior:

src/a.ts(2,10): error TS1005: ',' expected.
src/a.ts(2,20): error TS1005: ',' expected.
src/a.ts(2,21): error TS1128: Declaration or statement expected.
src/a.ts(2,22): error TS1128: Declaration or statement expected.
src/a.ts(2,28): error TS1109: Expression expected.
src/a.ts(3,8): error TS1005: ';' expected.
src/a.ts(3,14): error TS1109: Expression expected.
src/a.ts(4,1): error TS1128: Declaration or statement expected.

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

Start by compiling the provided TypeScript snippet and compare the diagnostic location and wording with the expected message. No source file or test is named in the issue, so trace the compiler path handling the optional property in the destructured parameter. Done means reporting the targeted error at the ? rather than the cascade of parse errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
compilers
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.