microsoft / microsoft/vscode-cpptools
Copilot Hover should better handle cases where symbols can't be resolved
Open
Nobody has claimed this yet.
bug
Feature: Copilot Hover
Language Service
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
When IntelliSense errors exist, we can end up passing information such as and as part of the declaration/definition, which leads to poor results.
We should either better handle this scenario or detect it and return the copilot hover unavailable error.
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 tracing the Copilot Hover path that consumes IntelliSense declaration or definition data, focusing on how unresolved symbols produce error-type and error-constant values. Reproduce the case with IntelliSense errors and verify that the result either handles those values appropriately or returns the Copilot hover unavailable error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100