Sonarly Claude Code
340874736d
https://sonarly.com/issue/31529?type=bug When a related record is soft-deleted, the relation cell shows a misleading "Not shared" lock icon instead of an empty/deleted state, because the frontend conflates soft-deletion with RLS permission denial. Fix: The fix is in the backend's `process-nested-relations-v2.helper.ts`, which resolves nested relation fields when fetching records. **What changed:** For MANY_TO_ONE relations (e.g., Opportunity → Person), the relation query now includes soft-deleted records by calling `.withDeleted()` on the TypeORM query builder. This means when a related record is soft-deleted (e.g., `timCook` is deleted), the query still finds it by its ID, and the frontend receives the record data. **Why this fixes the bug:** Previously, TypeORM's automatic `deletedAt IS NULL` filter excluded soft-deleted records from relation resolution. The foreign key (e.g., `personId = timCookId`) remained set, but the relation resolved to `null`. The frontend's `RelationToOneFieldDisplay` then detected `FK set + relation null` and showed "Not shared" (designed for RLS). With this fix, soft-deleted records are found and returned, so `fieldValue` is defined and the record chip renders normally. **Why only MANY_TO_ONE:** For ONE_TO_MANY relations (lists), including soft-deleted records would show deleted items in relation lists, which is undesirable. The flag `includeSoftDeletedRecords` is set to `true` only when `relationType !== ONE_TO_MANY`. **RLS behavior preserved:** The `withDeleted()` call only disables the soft-delete filter. RLS/row-level permission checks are applied at the repository layer via `rolePermissionConfig`, which remains unaffected.
The #1 Open-Source CRM
Website · 
Documentation · 
Roadmap · 
Discord · 
Figma
Why Twenty
Twenty gives technical teams the building blocks for a custom CRM that meets complex business needs and quickly adapts as the business evolves. Twenty is the CRM you build, ship, and version like the rest of your stack.
Learn more about why we built Twenty
Installation
Cloud
The fastest way to get started. Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date.
Build an app
Scaffold a new app with the Twenty CLI:
npx create-twenty-app my-app
Define objects, fields, and views as code:
import { defineObject, FieldType } from 'twenty-sdk/define';
export default defineObject({
nameSingular: 'deal',
namePlural: 'deals',
labelSingular: 'Deal',
labelPlural: 'Deals',
fields: [
{ name: 'name', label: 'Name', type: FieldType.TEXT },
{ name: 'amount', label: 'Amount', type: FieldType.CURRENCY },
{ name: 'closeDate', label: 'Close Date', type: FieldType.DATE_TIME },
],
});
Then ship it to your workspace:
npx twenty deploy
See the app development guide for objects, views, agents, and logic functions.
Self-hosting
Run Twenty on your own infrastructure with Docker Compose, or contribute locally via the local setup guide.
Everything you need
Twenty gives you the building blocks of a modern CRM (objects, views, workflows, and agents) and lets you extend them as code. Here's a tour of what's in the box.
Want to go deeper? Read the 
User Guide for product walkthroughs, or the Documentation for developer reference.
|
|
|
|
|
|
Learn more about version control in docStack
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 · Discord · 
Feature requests · Releases · 
X · 
LinkedIn · 
Crowdin · 
Contribute