debug extension / mode for content-mapper

[NullVoxPopuli]

🔍 搜索 Terms

content mapper

volar labs

• only result is API usage patterns for complex editor extensions #63800 -- which doesn't seem relevant

✅ 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-新建-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Volar has a really helpful tool for debugging mapping, here: https://volarjs.dev/core-concepts/volar-labs/

it would be great to have something similar for content-mappers

📃 Motivating Example

In a big project at work, I'm not seeing completions / hovers in VSCode, even though I have them in neovim and in smaller projects in vscode. the more debugging utilities available, the more I'd be able to narrow what the problem could be (config setup or otherwise)

💻 Use Cases

see above

[andrewbranch]

I have a prototype of one that I'm in the process of porting into the built-in TS extension. I was going to publish it separately but got feedback from the team that it would be good to include as a first-class thing.