yoavbls / yoavbls/pretty-ts-errors
Hide Unformatted TypeScript errors / move to after the pretty errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.1k
- Forks
- 111
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 5
Description
Really loving the format of these errors! It's a lot easier to read.
The only thing I noticed is that the unformatted errors are still showing up. Was this intended or is there a way to remove them?
Update / TLDR
This is currently intentional but there are plans to improve the experience. This could potentially be improved by:
- Removing the original error
- Changing the order of the errors so that the pretty version is on top
The issue is that the improvements rely on changes to VS Code. Go upvote this issue if you want these changes!
@yoavbls wrote:
This is the issue that will eventually allow us to modify the order of the errors + mute the original error:
https://github.com/microsoft/vscode/issues/54272
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 linked VS Code issue 54272, since the requested error ordering and removal of the original error depend on that change. Check whether VS Code now exposes the needed support; the issue is done when the pretty TypeScript error appears first and the unformatted original is removed or muted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100