microsoft / microsoft/vscode-cpptools
[internal] Update native tests to allow finer control of document visibility and activation.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
With the changes to populate IntelliSense progressively, we're now updating all visible (ranges of) documents (starting with the active document) instead of just updating the active document. We're also not processing an update on didOpen, but waiting until we receive visibility notification.
To avoid having to make significant changes to native tests, test's currently automatically make a file visible an active when opened.
This issue is tracking updating native tests to allow (and use) more explicit control over document visibility and activation.
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 reviewing the native test setup that currently makes a file visible and active when it is opened, along with the visibility notifications described in the issue. Update the tests so visibility and activation are controlled explicitly, and confirm they no longer depend on automatic activation while still covering progressive document updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100