microsoft / microsoft/TypeScript

Disable inlay hints for tests (or allow conditional overrides)

Open
#45,785 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

In Discussion Suggestion
Dominant language
Go
Stars
111k
Forks
14.4k
Avg merge
1d 19h
Merged PRs (30d)
117

Description

Suggestion

Originally opened at https://github.com/microsoft/vscode/issues/132304 - they asked me to file upstream.

🔍 Search Terms

inlay hints

✅ Viability Checklist

My suggestion meets these guidelines:

  • 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 feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

I ❤️ the new inlay hints feature. One area where it's a bit noisy is in tests, though. Even with the literals setting, it shows up for Jest (and similar) test blocks (describe, it, test). Please consider adding a way to override this for certain cases. Thank you!

image

📃 Motivating Example

As a developer, I want to maximize readability while minimizing noise.

💻 Use Cases

  • VSCode

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 files, tests, or entry points. Start by locating the TypeScript and JavaScript inlay-hints implementation, then review the linked VSCode context and TypeScript design goals. Done means supporting suppression or conditional overrides for test blocks such as describe, it, and test.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.