microsoft / microsoft/TypeScript
Indicate in the editor that a type is explicitly `any`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
🔍 Search Terms
any marker editor
✅ Viability Checklist
- This wouldn't be a breaking change in existing TypeScript/JavaScript code
- This wouldn't change the runtime behavior of existing JavaScript code
- This could be implemented without emitting different JS based on the types of the expressions
- This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals
⭐ Suggestion
Types that are explicitly set to any are sometimes hard to distinguish from actually typed variables in the editor. You might be adopting types while still having a lot of any around and then it would be helpful to call any out more explicitly in the editor.
📃 Motivating Example
I am now using the extension https://marketplace.visualstudio.com/items?itemName=danvk.any-xray which does this:
💻 Use Cases
- What do you want to use this for?
Seeing explicit any types easily so that I can work on adding types.
- What shortcomings exist with current approaches?
I can disable explicit any by producing errors but that is very aggressive.
- What workarounds are you using in the meantime?
Hovering over the type.
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
The issue describes an editor indication for explicitly declared any types and points to the any-xray extension as a reference. Start by tracing how TypeScript exposes type information to editors and reviewing related editor or language-service tests; done means the intended indication is implemented without changing runtime output and is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100