Sonarly Claude Code
eadfa26b70
https://sonarly.com/issue/18537?type=bug The `useRelatedRecordCommands` hook throws an unhandled error when a relation field on an object (e.g., `people`) references a target custom object that no longer exists in the metadata store, crashing the page. Fix: Two files changed to gracefully handle orphaned relation targets (relation fields that reference deleted/missing custom objects): 1. **`useRelatedRecordCommands.ts`** (line 60-64): Replaced `throw new Error(...)` with `continue`. When iterating ONE_TO_MANY relation fields to build command menu items, if the target object metadata is not found, the loop now skips that field instead of crashing the React render tree. This is the correct behavior — there's no command menu item to create for a non-existent object. 2. **`generateDepthRecordGqlFieldsFromFields.ts`** (line 57-61): Replaced `throw new Error(...)` with `return recordGqlFields` (the accumulator). Inside the `reduce`, when a relation field references a target object that doesn't exist in the metadata, we skip it and return the fields accumulated so far. This prevents the GraphQL field generation from crashing when building queries for objects with orphaned relations. Both cases are data consistency edge cases — not programming invariants. When a custom object is deleted, relation fields on other objects may temporarily still reference it (due to localStorage cache staleness or incomplete server-side cleanup). Crashing the entire page is disproportionate; skipping the orphaned field is the correct degraded behavior.
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!