microsoft / microsoft/TypeScript
Please provide better feedback for issue 20357
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
disableSizeLimit, "Find All References"
Suggestion
Issue #20357 is closed. That's great, what's not great is the poor error message feedback that the TS server provides. There is a project so telling the user there isn't one is confusing. The fix is not obvious and neither is the issue. Any chance of an improvement in the error text?
Use Cases
Examples
Checklist
My suggestion meets these guidelines:
- [ x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [ x] This wouldn't change the runtime behavior of existing JavaScript code
- [ x] This could be implemented without emitting different JS based on the types of the expressions
- [ x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
- [ x] This feature would agree with the rest of TypeScript's Design Goals.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the TypeScript server handling for the disableSizeLimit and "Find All References" search terms, then review issue #20357 for the related behavior. The work is complete when the server's feedback distinguishes the existing project situation clearly instead of reporting that no project exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100