Skip to content

fix: teach the extension about the new remotes config key - #3

Draft
ocauapaz wants to merge 1 commit into
mainfrom
claude/new-session-ndad70
Draft

fix: teach the extension about the new remotes config key#3
ocauapaz wants to merge 1 commit into
mainfrom
claude/new-session-ndad70

Conversation

@ocauapaz

@ocauapaz ocauapaz commented Aug 7, 2026

Copy link
Copy Markdown
Owner

Fixes the red VS Code extension job on CI #11 (7b5df1d, main).

What broke

8cd4468 added a remotes config key to the compiler. The extension keeps its own copies of that key list, and neither followed:

  • src/language.js — the completion list. The config key 'remotes' is documented test failed, which is the CI failure.
  • syntaxes/btyn.tmLanguage.json — the highlighting regex. Not caught by any test, but a key missing from that alternation falls through to the "unknown key" rule, so remotes = "..." was rendered as a typo in every schema that set it.

Changes

  • Add remotes to CONFIG_KEYS in src/language.js, with the default ("BTYN") and a hover doc matching the compiler's comment.
  • Add remotes to the config-key alternation in the grammar.
  • Add a grammar test asserting every key in the compiler's CONFIG_KEYS highlights as support.type.property-name. The grammar was only exercised against examples/net.btyn, which does not use every key — that is why this one slipped through while the completion list was checked.

Verification

npm test in editors/vscode: 65 passed in language.test.js (was 1 failed, 63 passed) and 60 passed in grammar.test.js. Reverting just the grammar line fails the new per-key case, so the test does catch the gap it was written for.

No compiler changes — the Compiler and codecs job was already green.


Generated by Claude Code

The compiler grew a `remotes` key, but the extension's two copies of the
key list did not follow: completion stopped offering it, and the grammar
flagged it as a typo in any schema that set it. CI caught the first.

The grammar was unchecked because only the example schema is tokenised,
and it does not set every key, so add a case per compiler key.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011WxNANvAqPzmAA4ws5FCcR
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants