Skip to content

fix(vscode): remove the legacy settings migration - #17

Merged
fi3ework merged 2 commits into
mainfrom
chore-remove-settings-migration
Aug 18, 2026
Merged

fix(vscode): remove the legacy settings migration#17
fi3ework merged 2 commits into
mainfrom
chore-remove-settings-migration

Conversation

@fi3ework

@fi3ework fi3ework commented Aug 18, 2026

Copy link
Copy Markdown
Member

Closes #15

What

Removes the settings migration from the retired standalone rstack.rslint / rstack.rstest extensions:

  • packages/vscode/src/migration.ts and tests/migration.test.ts deleted (LEGACY_MAPPINGS, the planner, the prompt, PROMPT_DISMISSED_KEY).

  • rstack.migrateSettings dropped from contributes.commands, the shell's command registration and the status-bar hover (which now lists two shell actions; the row-count assertions and the hover comments follow).

  • The activation-time prompt is gone from ExtensionShell.activate().

  • packages/vscode/AGENTS.md: adaptation ci: bump actions/upload-artifact to v7 for the Node 24 runtime #2 and the pre-1.0 rule no longer refer to a migration mapping; CONTEXT.md's Shell entry likewise.

  • packages/vscode/README.md: the "Migrating from the standalone extensions" section is replaced by a one-paragraph "Coming from the standalone extensions" note — settings and keybindings are re-entered under rstack.*, and rslint.binPath / customBinPath point at rstack.rslint.corePath instead. This resolves the issue's open question in favour of keeping the note.

  • docs/adr/0001 / 0002: the parentheticals saying rstest.nodeExecutable "migrates to" rstack.nodeExecutable now say the legacy key had the same role and is not migrated — this repo keeps ADRs current (0001 was already amended by feat(vscode): format through rs fmt --lsp on the User Node runtime #12 and feat(vscode): lint through an editor-shipped worker and bridge define.lint() #14), so a stale mechanism description would conflict with the code.

Verification

  • pnpm lint (rs lint --type-check): 0 errors, 0 type errors.
  • pnpm test:unit: all passing.
  • VSCODE_CLI=1 pnpm test:e2e vscode (shell/detection/fmt suites, covers the command registration and status bar): exit 0.
  • rs fmt --check: clean.

Drop `migration.ts`, its tests, the `rstack.migrateSettings` command (manifest entry, palette registration and status-bar hover action) and the activation-time prompt with its `rstack.migration.dismissed` state.

Pre-1.0 the extension owes no compatibility to earlier states, and the migration only served users of the two retired standalone extensions; keeping it meant every settings change carried a mapping-table update plus tests for a one-off flow, and the table already had to model dropped features (`rslint.binPath` / `customBinPath`, #14). The README keeps a one-paragraph note telling standalone-extension users to re-enter their settings under `rstack.*` and re-bind keybindings; AGENTS.md's namespace adaptation and pre-1.0 rule are reworded so no migration is implied.

Closes #15
ADR 0001 and 0002 said the standalone Rstest extension's `rstest.nodeExecutable` "migrates to" `rstack.nodeExecutable`; the migration was removed in #15, so the parentheticals now state only that the legacy key had the same role.
@fi3ework fi3ework changed the title chore(vscode): remove the legacy settings migration fix(vscode): remove the legacy settings migration Aug 18, 2026
@fi3ework
fi3ework enabled auto-merge (squash) August 18, 2026 07:29
@fi3ework
fi3ework merged commit bf4ddfb into main Aug 18, 2026
3 checks passed
@fi3ework
fi3ework deleted the chore-remove-settings-migration branch August 18, 2026 07:30
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.

vscode: remove the legacy settings migration

1 participant