Test: Notebook CodeActions (Finalized API)

[Yoyokrazy]

Refs: #193120, #179213

• anyOS @jrieken
• anyOS @sbatten

Complexity: 3

author: @Yoyokrazy

Create Issue

---

Summary:

The API has been finalized for support notebook CodeActions, now giving users the option to use the top-level kind CodeActionKind.Notebook when creating CodeAction providers. See more details in #193120.

Steps to Test:

• Download or create your own extension, creating a provider for both cell/source and Notebook CodeActions
  • This is a sample extension that has two providers defined.
  • GHINB also has a Notebook CodeAction provider in this branch, as defined here.
• Launch the extension host.
• Create a new or open a pre-existing notebook
  • This is a playground I use with a couple messy notebooks that can be tested on.
• Go to Settings (UI) and search for notebook.codeActionsOnSave and add your CodeActions.
  • If you use the sample extension, your settings.json could include something like this to test both Cell and Notebook scopes:

"notebook.codeActionsOnSave": {
	"notebook.source.cleanImports": "explicit", // this is a notebook CodeAction.
	"source.sampleCodeAction": "explicit", // this is a standard CodeAction, applied against all cells in parallel.
},

• Save the document, triggering the CodeActions. May be easier to ensure they work individually by commenting one or the other CodeAction within your settings, then testing them combined at the end.

---

Thanks so much for testing!