microsoft / microsoft/TypeScript

Provide suggested fixes for unresolved entities

Open
#4,370 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Something like the following:

![image](https://cloud.githubusercontent.com/assets/972891/9373302/c205a9c8-469d-11e5-929f-80988968fb77.png)

See https://github.com/Microsoft/TypeScript-Sublime-Plugin/issues/327 for the original suggestion.

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

The issue names no source file, test, or entry point. Start by reviewing the linked TypeScript-Sublime-Plugin issue and the attached example to determine which unresolved entities need suggestions and where TypeScript exposes them; done means the requested suggested fixes are implemented and verified by appropriate tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
compilers, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.