microsoft / microsoft/TypeScript

Offer an auto-import for unresolved shorthand-named object literal properties

Open
#32,219 9 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

suppose I have exported an object called Foo in foo.js, and in another file I want to use something like this:

export default configure({Foo})

autocomplete will not show Foo and of course, will not auto import from that file.
to use auto import, I have to write the code like this:

export default configure({Foo:Foo})

actually autocomplete shows Foo, But it doesn't auto import. it has abc icon.
could you support object shorthand in autocomplete?

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 reproducing the two JavaScript examples in the TypeScript language-service autocomplete flow and compare the shorthand property with the explicit Foo:Foo form. Done means autocomplete offers the exported Foo and provides the corresponding auto-import for the shorthand object property.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
developer-experience, tooling
Issue type
Feature
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.