Sonarly Claude Code 34ef01b9ed fix: restore chip count display for relation-to-many fields in unfocused table cells
https://sonarly.com/issue/15886?type=bug

Table performance optimization replaced dynamic focus state with static unfocused provider, causing the ExpandableList "+N" overflow count to never display in non-hovered cells. Overflowing relation chips are hidden with no visual indicator.

Fix: The table performance optimization in commit 159bb9d70a replaced the dynamic `FieldFocusContextProvider` (with `useState`) with `FieldFocusStaticUnfocusedProvider` (hardcoded `isFocused: false`). This broke `RelationFromManyFieldDisplay`, `MorphRelationOneToManyFieldDisplay`, and `MultiSelectFieldDisplay` which all passed `isChipCountDisplayed={isFocused}` to `ExpandableList`.

When `isChipCountDisplayed` is explicitly `false`, `ExpandableList` both:
1. Hides the "+N" overflow count badge (line 95: `canDisplayChipCount = false`)
2. Disables its internal mouse hover fallback (lines 130-138: `onMouseEnter`/`onMouseLeave` set to `undefined`)

The fix removes the `isChipCountDisplayed` prop from all affected `ExpandableList` usages. When the prop is `undefined`, `ExpandableList` falls back to its internal hover detection via `onMouseEnter`/`onMouseLeave`, which correctly shows the "+N" count on hover. This is the same pattern already used by `LinksDisplay`, `FilesDisplay`, and `ArrayDisplay`.

Additionally, `MultiSelectFieldDisplay` had a dead branch (`isFocused ? <ExpandableList> : <MultiSelectDisplay>`) where the `ExpandableList` path was never reached. The fix always renders `ExpandableList`, consistent with the other display components.

Removed unused imports: `useFieldFocus`, `styled` from `@linaria/react`, `themeCssVariables`, `StyledContainer` styled component, and `MultiSelectDisplay`.
2026-03-18 10:37:18 +00:00
2025-08-07 17:02:12 +02:00
2025-07-08 15:13:02 +02:00
2026-03-11 16:30:28 +01:00

Twenty logo

The #1 Open-Source CRM

🌐 Website · 📚 Documentation · Roadmap · Discord · Figma


Cover


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

Companies Kanban Views

Customize your objects and fields

Setting Custom Objects

Create and manage permissions with custom roles

Permissions

Automate workflow with triggers and actions

Workflows

Emails, calendar events, files, and more

Other Features


Stack

Thanks

Chromatic Greptile Sentry Crowdin E2B

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

Languages
TypeScript 78%
MDX 18.5%
JavaScript 3.1%
Python 0.2%