Test: Multi-Document Occurrence Highlighting

[Yoyokrazy]

Refs: #198469, #196354

• anyOS @jrieken
• anyOS @cwebster-99

Complexity: 3

author: @Yoyokrazy

Create Issue

---

Summary:

This iteration we introduced API to contribute multi-document highlight providers. As a first step, the typescript-language-features builtin extension now registers a multi-document provider, and supports semantic highlighting out of the box accross multiple files. This is driven by the Editor: Occurrences Highlight enum setting. This TPI is meant to test the behavior of the new semantic provider and the textual providers that lie underneath as a fallback.

Steps to Test:

• Paste the following into your settings.json file: "editor.occurrencesHighlight": "multiFile"
• Open multiple files in your workspace, several Typescript files, a notebook, and a file of another language (python, rust, etc).
• Highlight a variable inside the typescript file that you would expect to have semantically highlighted accross the two .ts files. (ex: a class definition in one file, and an object of that class in another file). Ensure that only semantic occurrences are highlighted here, and the class name isn't highlighted within a comment elsewhere.
• Click an import statement within a typescript file and ensure that the word "import" is not highlighted across multiple files.
• Ensure that while using semantic highlighting in a ts file, you are not getting highlights within non-ts files even if they contain the variable name.
•  Highlight a variable within a notebook (this will use a textual occurrence provider) and ensure that the highlights carry across cells, but do not carry over into any other files or notebooks.
• Continue highlighting with different workspace states and ensure that the standard highlights within your single file are navigable and are being presented as expected.

Please file issues if there is unexpected behavior or UX bugs!

---

Thanks so much for testing!

[cwebster-99]

LGTM!