Skip to content

chore(vscode): complete the Marketplace manifest for the first release - #19

Merged
fi3ework merged 2 commits into
mainfrom
chore/marketplace-manifest
Aug 18, 2026
Merged

chore(vscode): complete the Marketplace manifest for the first release#19
fi3ework merged 2 commits into
mainfrom
chore/marketplace-manifest

Conversation

@fi3ework

Copy link
Copy Markdown
Member

Preparation for publishing `rstack.rstack@0.1.0` to the VS Code Marketplace and Open VSX.

Changes (package.json only)

  • `preview: true` — the extension is pre-1.0 and breaks freely (per AGENTS.md); the Marketplace shows a Preview badge.
  • `qna` → GitHub Issues, so questions land where they are actually read instead of the Marketplace Q&A tab.
  • `capabilities.virtualWorkspaces: { supported: false }` — the extension resolves `@rslint/core`, `@rstest/core` and `rstack` from the workspace's `node_modules` and spawns them as local processes; VS Code's default (`true`) would let it activate in github.dev-style workspaces where it cannot work. `untrustedWorkspaces` was already declared.
  • Add the missing top-level `description` for `rstack.rstest.testCaseCollectMethod` (the Settings UI showed only the per-value labels).

Checked against the docs

  • VS Code extension manifest reference: required fields (`name` lowercase, `version`, `publisher`, `engines.vscode`) and the presentation fields (`displayName`, `description`, `categories`, `keywords`, `icon` ≥128px, `license`, `repository`/`bugs`, `preview`, `qna`, `capabilities`) — all present now.
  • Brand casing matches upstream READMEs / rstack.rs: `Rstack`, `Rslint`, `Rstest`, `rs fmt`.
  • Open VSX: needs `publisher` = existing namespace (`rstack`, verified) and a license (MIT, `LICENSE.txt` is packaged) — satisfied.

Kept: version `0.1.0`, displayName `Rstack`.

Verification

  • `pnpm lint && pnpm test:unit && pnpm fmt:check` green.
  • `vsce package --target darwin-arm64` succeeds; the VSIX manifest carries `GalleryFlags: Public Preview`, `CustomerQnALink`, and `Links.Support`.
  • No E2E run: the change is declarative manifest metadata with no behavior in the local-file-system E2E environment.

- Flag the extension as preview while it is pre-1.0 and breaks freely.
- Point Q&A at GitHub Issues instead of the unmonitored Marketplace Q&A.
- Declare virtualWorkspaces: false — the extension resolves @rslint/core,
  @rstest/core and rstack from the workspace's node_modules and spawns them
  as local processes, so it cannot work without a real file system.
- Add the missing top-level description for
  rstack.rstest.testCaseCollectMethod so the Settings UI shows what the
  setting decides, not only the per-value labels.

@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: 5db793d5f7

ℹ️ 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/package.json Outdated
The shell always activates (packages/vscode/AGENTS.md) and detection already
skips non-file workspace folders, so in a virtual workspace the status bar
item still shows while no stack starts. `supported: false` would stop VS Code
from activating the extension there at all; `limited` describes what
actually happens.
@fi3ework
fi3ework merged commit fc005ae into main Aug 18, 2026
3 checks passed
@fi3ework
fi3ework deleted the chore/marketplace-manifest branch August 18, 2026 16:02
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.

1 participant