microsoft / microsoft/TypeScript
Inlay hints will be disabled after extending constructor function in Mixin Implementation using Typescript
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Version: 1.97.2
- OS Version: Windows_NT x64 10.0.26100
Steps to Reproduce:
Pre-conditions:
- Inlay hints must be enabled in VS Code
- Configurations of Inlay hints in VS Code
1. Make a function
3. Convert function to Generic and constructor function
- Before extending constructor function (Inlay hints are enabled)
- After extending constructor function (Inlay hints are disabled)
Recorded Video
https://github.com/user-attachments/assets/897fea39-0edc-4a7f-a88f-c91fc6636ace
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 reproducing the report with inlay hints enabled, then compare the generic constructor-function example before and after extending the constructor in the mixin implementation. Trace the TypeScript language-service path that computes inlay hints for this construct. Done means hints remain enabled after the extension and the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100