René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Changing rstack.rslint.trace.server restarts every stack instead of updating trace in place","articleBody":"## Problem\n\nChanging `rstack.rslint.trace.server` restarts the whole extension instead of updating the trace level in place.\n\n`trace.server` is listed in the Rslint controller's `restartOnSettings` (`packages/vscode/src/stacks/lint/index.ts:71-75`). The shell answers any matching configuration change with `restart(undefined, …)` (`packages/vscode/src/extension.ts:73-110`), which expands to every stack (`extension.ts:248-257`). So flipping a debug-only setting from `off` to `messages`:\n\n1. retires Rslint, Rstest and fmt (status bar goes to `starting`),\n2. sends `didClose` for every open document and deletes its diagnostics,\n3. disposes the Rstest `TestController` (the Test Explorer tree is destroyed and rebuilt),\n4. stops every fmt server,\n5. re-runs detection and rebuilds all three stacks.\n\nThe replacement client only attaches a trace channel and calls `client.setTrace` when the setting is non-`off` at construction time (`packages/vscode/src/stacks/lint/Rslint.ts:415-445,509-514`), so there is no path to enable tracing on a running client.\n\n## Upstream behavior\n\nThe standalone rslint extension supplied a `traceOutputChannel` unconditionally and let `vscode-languageclient` own the setting: it puts the initial value into the `initialize` request's `trace` field and sends `$/setTrace` on every later change, with no restart (`rslint@origin/main:packages/vscode-extension/src/Rslint.ts:96-119,429-434`). Its E2E asserts that `off → messages → verbose → off` reaches every running client via `$/setTrace` while each server's start count stays at 1 (`packages/vscode-extension/__tests__/suite-jsconfig/trace-output-channel.test.ts:200-300`).\n\n## Proposal\n\n- Drop `trace.server` from `restartOnSettings` in `stacks/lint/index.ts`.\n- Pass the trace channel to the language client unconditionally so `vscode-languageclient` handles `$/setTrace` itself; remove the manual `setTrace` call.\n- Keep the shared `Rstack: Rslint` channel for trace output (the four-channel layout in `channels.ts` is a deliberate cap and unrelated to whether a restart is needed).\n- Add an E2E in `e2e/lint/` mirroring the upstream assertions: changing the setting notifies running clients and does not restart any server.\n- Check whether `rstack.fmt.trace.server` has the same issue and apply the same fix.\n\n## Context\n\nFound while auditing the standalone rslint/rstest extensions for sunset. This is the only confirmed behavior regression relative to the standalone extensions.\n","author":{"url":"https://github.com/fi3ework","@type":"Person","name":"fi3ework"},"datePublished":"2026-09-03T08:13:27Z","url":"https://github.com/rstackjs/rstack-editor/issues/39"}