fix: preserve Zed settings during connect#953
Conversation
Signed-off-by: Igor Arkhipov <igor.arkhipov@joinhandshake.com>
|
@IgorArkhipov is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughAdds ChangesJSONC-safe Zed settings merge
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
settings.jsoncontent when addingcontext_servers.agentmemoryRoot Cause
agentmemory connect zedused the shared JSON MCP adapter, which parsed settings with strictJSON.parse. Zed settings may be JSONC, so comments or trailing commas caused parsing to fail. The adapter then treated the existing file as missing/empty and wrote a fresh config containing onlycontext_servers.agentmemory.Validation
npm run buildnpm test -- test/connect-new-agents.test.tsnpm testFixes #952
Summary by CodeRabbit
New Features
Improvements