Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable better default formatters for text types in debug variables #242492

Closed
timheuer opened this issue Mar 3, 2025 · 3 comments
Closed

Enable better default formatters for text types in debug variables #242492

timheuer opened this issue Mar 3, 2025 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@timheuer
Copy link
Member

timheuer commented Mar 3, 2025

VS Code debugger experience lacks a common tooling experience in visualizing language-agnostic and common formats when debugging and providing a delightful experience for strings.

Take into account a string variable that is JSON (serialized to string), the default experience in VSCode is a blob of string text or default "view as HEX" both of which are not as helpful.

Considering Visual Studio's text implementation (for all languages, default in the shell), it enables visualization of very common formats of JSON, XML, JWT tokens, etc.:

https://learn.microsoft.com/en-us/visualstudio/debugger/string-visualizer-dialog-box?view=vs-2022#text-string-data

Image

Adding string to JSON/XML/JWT would be a value-add for the default debugger experience in variables, while still delegating custom language-specific visualizers to the languages themselves (e.g., IEnumerable for C#, etc.)

@roblourens
Copy link
Member

I think this could fall under #197287 @connor4312?

@connor4312
Copy link
Member

Yes, that's exactly that issue I think

@connor4312 connor4312 added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 3, 2025
Copy link

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants