registrystack / registrystack/registry-stack
Publish the Registry Stack extension for Zed
- 主要言語
- Rust
- スター
- 2
- フォーク
- 0
- 平均マージ
- 2時間 55分
- マージ済み PR(30日)
- 130
説明
Tracked by #399. Depends on #394 and #393.
## Outcome
Zed users can install a Registry Stack extension that attaches the shared project language server to Registry Stack YAML while retaining Zed's native YAML support.
Depends on the schema-driven baseline and shared Registry Stack language server.
## Requirements
- Register and launch the shared Registry Stack language server for the applicable YAML language.
- Preserve Zed's native YAML grammar, formatting, and yaml-language-server features.
- Activate project intelligence only within a detected Registry Stack project.
- Discover a compatible installed `registryctl` or language-server binary in accordance with Zed extension packaging rules.
- Provide an actionable status/error message for a missing binary or incompatible version.
- Support project-local settings without machine-specific committed paths.
- Publish through the Zed extension registry after local development-extension verification.
## Acceptance criteria
- [ ] Installing the extension in a clean supported Zed environment enables schema-driven editing and project navigation for a sample project.
- [ ] Normal YAML behavior remains available and unrelated YAML workspaces are unaffected.
- [ ] Language-server startup, restart, missing binary, and version mismatch paths are tested.
- [ ] Project-local schema settings and language-server settings do not require absolute paths.
- [ ] The extension performs no implicit live test, credential read, or network access during project analysis.
- [ ] macOS and supported Linux installation paths are documented and smoke-tested.
- [ ] Publication metadata, licensing, ownership, and release steps are documented.
## Non-goals
- Reimplementing authoring semantics in the Zed extension
- Shipping a divergent Zed-only language server
- Replacing Zed's YAML grammar or formatter
コントリビューションガイド
調査の方向性
まず #394 のスキーマ駆動のベースラインと #393 の共有 language server を読み、その後 Zed 拡張機能のパッケージングルールを確認します。YAML の保持、プロジェクト検出、バイナリエラー、設定、インストールパス、公開ドキュメントを含む、記載された受け入れ基準に対して、クリーンな Zed 環境で拡張機能を検証します。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- yaml
- 領域
- developer-experience, tooling
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 静か
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100