Add setting and command to show/hide cells in outline

[vezwork]

Fixes #647

Kapture.2026-05-08.at.12.51.44.mp4

• Adds a symbols.showCodeCellsInOutline setting to the Quarto configuration,
• Adds a quarto.toggleCodeCellsInOutline command to toggle that setting.

Note: I attempted to add tests but for some reason in the tests the outline / document symbols refuse to change. I tried many things including waiting longer during the test after calling quarto.toggleCodeCellsInOutline, programmatically getting document symbols with vscode.executeDocumentSymbolProvider, looking with my own eyes at the outline during the test. I'm not sure why it doesn't work in the test environment!

[posit-snyk-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[juliasilge]

This setting right now is only read when we start the app, so the experience is that the user changes the setting but doesn't observe the behavior change. I think we need to either:

• add a listener for config change for this setting, OR
• add a note to the setting description like "Restart to apply" or similar

[vezwork]

This setting right now is only read when we start the app, so the experience is that the user changes the setting but doesn't observe the behavior change.

In my testing in both VSCode and Positron, when I use the "Quarto: Toggle Code Cells in Outline" command the change in the outline is instantly reflected. Are you not experiencing that in your testing? Or do you mean if the user changes the setting manually we should notify them to restart?

[juliasilge]

Or do you mean if the user changes the setting manually we should notify them to restart?

Yep, that's right. Right now, if the user changes the setting, nothing happens until the next time they close/open the app or reload the window. I think the best choice is to use vscode.workspace.onDidChangeConfiguration and a listener like if (event.affectsConfiguration("quarto.symbols.showCodeCellsInOutline")). A less good option that would still be acceptable is to put a note on the setting description that the user will need to restart VS Code/Positron to see the change in behavior.

It also would be worth re-examining the no-op edit hack and seeing if we can either:

• have the client send a workspace/didChangeConfiguration to the LSP to retrigger the outline generation, OR
• in the config listener, call vscode.commands.executeCommand("vscode.executeDocumentSymbolProvider", uri) on the active doc, so the toggle command just flips the setting, and the listener owns the refresh