Fix symbol anchor rendering by using Location instead of SymbolInformation in value property #2950
+131
−1
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.
Symbol links in chat output (e.g., "activate function") failed to open with "Unable to resolve resource" errors showing malformed URIs like
c:%5CUsers%5C....Root Cause
ChatResponseAnchorPartwas constructed withSymbolInformationcast toanywhere VS Code expectsUri | Location, causing the chat UI to extract properties incorrectly.Changes
File:
src/extension/linkify/common/responseStreamWithLinkification.tssymbolInformation.locationto constructor for thevalueproperty (backward compatible)value2property to fullSymbolInformationfor proper symbol rendering (proposed API)This aligns with
vscode.proposed.chatParticipantAdditions.d.tswherevalue2supportsUri | Location | SymbolInformation.Testing
Added
responseStreamWithLinkification.spec.tswith tests covering:value(Location) andvalue2(SymbolInformation)value2Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.