Sonarly Claude Code
48eda24c8c
https://sonarly.com/issue/34231?type=bug The eleven button components in twenty-ui implement disabled, loading, hover, and active states inconsistently, causing disabled buttons to appear clickable and loading states to be absent from most button types. Fix: Fixed three button components in `twenty-ui` to properly suppress hover effects when disabled and use correct disabled state colors, matching the reference implementation in `Button.tsx`: **MainButton.tsx** — The `secondary` variant's hover handler did not check the `disabled` prop, so disabled secondary buttons showed a hover background change (`background.tertiary`) making them appear interactive. Fixed by returning the variant's normal (non-hover) background when disabled — `background.secondary` for primary variant, `background.primary` for secondary variant — so the hover produces no visual change on disabled buttons. This affects auth/onboarding pages where MainButton is heavily used. **InsideButton.tsx** — The hover handler unconditionally applied `background.transparent.light` regardless of disabled state. Fixed by adding a `disabled` prop check that returns `'transparent'` when disabled, matching the pattern used in LightButton, LightIconButton, FloatingButton, and FloatingIconButton. **AnimatedButton.tsx** — Two fixes aligned with corresponding fixes already made to Button.tsx: 1. Primary/blue disabled background now uses `accent.accent4060` (a dimmed blue) instead of the full `color.blue`, matching Button.tsx's fix from commit `3e9bff22bb`. 2. Secondary/tertiary danger disabled color now uses `color.red5` (a dimmed red) instead of the full `font.color.danger`, matching Button.tsx's fix from commit `2ac93bd803`.
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