Fix type graph viewer to display scopeless decorator state#9541
Open
Fix type graph viewer to display scopeless decorator state#9541
Conversation
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
packages/html-program-viewer/src/react/js-inspector/object-inspector.test.tsx
Outdated
Show resolved
Hide resolved
packages/html-program-viewer/src/react/js-inspector/object-inspector.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix bug with scopeless clientName in type graph
Fix type graph viewer to display scopeless decorator state
Jan 30, 2026
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Member
|
/azp run typespec - pr tools |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
You can try these changes here
|
packages/html-program-viewer/src/react/js-inspector/object-inspector.tsx
Show resolved
Hide resolved
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Contributor
Author
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Member
Member
|
@copilot you need to add a changelog |
commit: |
Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>
Contributor
Author
Contributor
|
All changed packages have been documented.
Show changes
|
.chronus/changes/fix-symbol-decorator-state-display-2026-02-02-13-19-46.md
Outdated
Show resolved
Hide resolved
Contributor
|
/azp run typespec - PR Tools |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Fix type graph viewer to display scopeless decorator state
Scopeless decorators (e.g.,
@clientName("enabled")without ascopeparameter) store their state using Symbol keys. The type graph viewer's ObjectInspector and ObjectPreview only iterated over string properties viaObject.getOwnPropertyNames()andfor...inloops, causing Symbol-keyed decorator state to appear empty in both expanded and collapsed views.Changes:
object-inspector.tsxusingObject.getOwnPropertySymbols()object-preview.tsxto show Symbol properties in collapsed viewgetPropertyValue()inproperty-utils.tsxto acceptstring | symbolsortObjectKeysis enabledExample:
Previously, the decorator data would render as
Symbol(...): { }in both collapsed and expanded views. Now it correctly displays the decorator properties in both the collapsed object preview and the expanded inspector view.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.