Sonarly Claude Code
d914039d45
https://sonarly.com/issue/18992?type=bug When an SSE event delivers a record update containing custom fields that are not yet present in the frontend's cached object metadata, `computeOptimisticRecordFromInput` throws a fatal error that breaks SSE event processing for the session. Fix: Replaced `throw new Error(...)` with `console.warn(...)` in `computeOptimisticRecordFromInput` when unknown fields are detected in the record input. **Why this is safe:** The function's main for-loop (line 80) iterates only over `objectMetadataItem.fields`, not over `recordInput` keys. Unknown fields in `recordInput` are naturally skipped by the loop and never processed. The throw was a defensive assertion added in commit `29745c6756` for mutation-triggered optimistic updates where the frontend controls the input. When SSE real-time events were added, this function started receiving server-controlled input that may include custom fields not yet in the frontend's stale metadata cache. **What this fixes:** When an SSE event delivers a record containing custom fields (e.g., `mail`, `pitched`, `media`, `number`, `businessCategory` on the `company` object) and the frontend's metadata cache hasn't refreshed yet, the function now logs a warning and continues processing known fields instead of crashing the entire SSE event stream handler. Updated the test from asserting a throw to asserting a `console.warn` call and verifying that known fields are still correctly processed while unknown fields are skipped.
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See: 🚀 Self-hosting 🖥️ Local Setup
Why Twenty
We built Twenty for three reasons:
CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.
A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.
We believe in open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
What You Can Do With Twenty
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Personalize layouts with filters, sort, group by, kanban and table views
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
- Star the repo
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!