Skip to content

fix(vscode): apply trace.server live, drop stale rslint.json watcher, port unicode-bom E2E - #44

Merged
fi3ework merged 3 commits into
mainfrom
fix/lint-trace-json-watcher-bom
Sep 3, 2026
Merged

fix(vscode): apply trace.server live, drop stale rslint.json watcher, port unicode-bom E2E#44
fi3ework merged 3 commits into
mainfrom
fix/lint-trace-json-watcher-bom

Conversation

@fi3ework

@fi3ework fi3ework commented Sep 3, 2026

Copy link
Copy Markdown
Member

Summary

  • Apply rstack.rslint.trace.server live through vscode-languageclient, without restarting the language server.
  • Scope rstack.rslint.trace.server to the window, matching vscode-languageclient's URI-less configuration lookup and the existing rstack.fmt.trace.server scope.
  • Remove the stale rslint.json / rslint.jsonc config-refresh watcher entries now that Rslint no longer loads legacy JSON configs.
  • Port Rslint's Unicode BOM E2E coverage, preserving this extension's diagnostic-code adaptation.

Upstream provenance: rslint #1967 for live LSP tracing, rslint #1951 for removing legacy JSON config loading, and rslint #1560 for the Unicode BOM rule and editor coverage.

The language client id changes from rslint to rstack.rslint because vscode-languageclient derives the trace setting namespace from that id. Without the rename, it would watch the unsupported rslint.trace.server key instead of rstack.rslint.trace.server.

Related Links

Closes #39

Closes #41

Closes #42

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).

Testing

  • pnpm lint — exit 0: Found 0 lint errors, 0 type errors and 0 warnings (linted 165 files with 22 rules, type-checked 156 files in 290ms using 14 threads).
  • pnpm test:unit — exit 0: 31 test files passed and 264 tests passed.
  • RSTACK_LINT_E2E_SUITES="Trace output,unicode-bom,No config,JS config" VSCODE_CLI=1 pnpm test:e2e lint — exit 0: JS config, Trace output channel, No config, and unicode-bom suites all passed.
  • Rstack lint bridge suite: covered by CI after the rebase onto main (fixed there by chore: latest Rstack toolchain everywhere, exact fixture pins, Renovate bumps fixtures too #46).

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 3, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-03T13:05:24.964021Z 59ade6c New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@fi3ework
fi3ework force-pushed the fix/lint-trace-json-watcher-bom branch from 591062f to 59ade6c Compare September 3, 2026 12:59

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 59ade6c18f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread packages/vscode/src/stacks/lint/Rslint.ts
@fi3ework
fi3ework merged commit 7c5d45b into main Sep 3, 2026
3 checks passed
@fi3ework
fi3ework deleted the fix/lint-trace-json-watcher-bom branch September 3, 2026 13:58
@fi3ework fi3ework mentioned this pull request Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant