microsoft / microsoft/TypeScript

Error message displays computed name '[attr]' instead of key value

Open
#57,653 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Experience Enhancement Help Wanted Suggestion
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
1d 19h
Merged PRs (30d)
117

Description

🔎 Search Terms

computed property, error message

🕗 Version & Regression Information
  • This is the behavior in every version I tried, and I reviewed the FAQ for entries about computed properties
⏯ Playground Link

https://tsplay.dev/WyV2bw

💻 Code
type Unit =
  | {
      name: string;
      stength: number;
    }
  | {
      name: string;
      magic: number;
    };

const createUnit = (
  name: string,
  attr: "strength" | "magic",
  power: number,
): Unit => {
  return attr === "strength"
    ? { name, [attr]: power } // <-- error here
    : { name, [attr]: power };
};
🙁 Actual behavior

Error message displays "Object literal may only specify known properties, and '[attr]' does not exist in type 'Unit'".

🙂 Expected behavior

Error message should display that "strength" doesn't exist on Unit. (and possibly even recommend "stength" instead)

Additional information about the issue

No response

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 diagnostic from the TypeScript code sample in the linked Playground and compare the actual '[attr]' message with the expected 'strength' wording. Trace the computed-property error reporting path in the compiler and add coverage for the shown example, including the suggested 'stength' spelling if supported. Done means the diagnostic reports the resolved key value rather than the source expression.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.