fix(marketplace): use relative paths for plugin source fields#17
fix(marketplace): use relative paths for plugin source fields#17AnExiledDev merged 1 commit intomainfrom
Conversation
All 11 plugin source fields in marketplace.json used bare names
(e.g., "codeforge-lsp") instead of relative paths ("./plugins/codeforge-lsp").
This caused `claude plugin marketplace add` to fail schema validation,
preventing plugins from registering correctly.
Closes #16
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughUpdates plugin source field references in the marketplace configuration from bare plugin names to relative paths (e.g., Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
sourcefields inmarketplace.jsonused bare names (e.g.,"codeforge-lsp") instead of relative paths ("./plugins/codeforge-lsp")claude plugin marketplace addto fail schema validation, preventing plugins from registering./plugins/prefix matching thepluginRootdeclarationCloses #16
Test plan
devcontainer up→ verify setup log shows all plugins installedclaude plugin marketplace listshows devs-marketplace with correct plugin countSummary by CodeRabbit
Bug Fixes
Documentation