Sonarly Claude Code
e31ece6e36
https://sonarly.com/issue/33889?type=bug When a user tries to add a second filter condition on a field that already has a filter, the existing filter is loaded for editing instead of a new one being created. This forces users into the Advanced Filters UI for a basic AND-combination use case. Fix: Removed the `findDuplicateRecordFilterInNonAdvancedRecordFilters` check from `useInitializeFilterOnFieldMetadataItemFromViewBarFilterDropdown`. This check was the root cause of the bug: when a user selected a field that already had a filter from the "+ Filter" dropdown, the hook would load the existing filter for editing instead of creating a new one, causing the existing filter condition to be overwritten. **What changed:** 1. **`useInitializeFilterOnFieldMetadataItemFromViewBarFilterDropdown.ts`**: Removed the `findDuplicateRecordFilterInNonAdvancedRecordFilters` call and the `if (filterIsAlreadyInCurrentRecordFilters)` branch. Now the hook always initializes a fresh filter with the default operand, regardless of whether a filter for the same field already exists. This allows users to add multiple filter conditions on the same field (e.g., "Name contains agency" AND "Name does not contain freelance"). Removed unused imports: `currentRecordFiltersComponentState`, `findDuplicateRecordFilterInNonAdvancedRecordFilters`, `isDefined`. 2. **Test file**: Updated the "duplicate field on city" test to verify the new behavior — selecting a field that already has a filter should NOT reuse the existing filter, but instead initialize a new one with the default operand. The `findDuplicateRecordFilterInNonAdvancedRecordFilters` utility is now dead code (no callers), but was left in place as it may still be useful for other features or could be referenced in Advanced Filters code.
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