Sonarly Claude Code d9757c2da7 fix: move droppable placeholder back inside innerRef container in Kanban board
https://sonarly.com/issue/17390?type=bug

Kanban board drops only register near the top of target columns because the `@hello-pangea/dnd` placeholder was moved outside the `innerRef` container, breaking the library's droppable area measurement.

Fix: **What changed:**

Moved `droppableProvided.innerRef` and `droppableProvided.droppableProps` from `StyledColumnCardsContainer` (inside the memo boundary) up to `StyledColumn` in `RecordBoardColumn.tsx` (outside the memo boundary). This ensures both the card list and the placeholder are children of the `innerRef` element, which is required by `@hello-pangea/dnd` for correct droppable area measurement.

**RecordBoardColumn.tsx:**
- Added `ref={droppableProvided.innerRef}` and `{...droppableProvided.droppableProps}` to `StyledColumn`
- Removed `droppableProvided` from props passed to `RecordBoardColumnCardsContainer`

**RecordBoardColumnCardsContainer.tsx:**
- Removed `droppableProvided` from component props and type definition
- Removed `ref` and spread of `droppableProps` from `StyledColumnCardsContainer`
- Removed unused `DroppableProvided` type import

**Why this works:**
The `DragAndDropLibraryLegacyReRenderBreaker` (React.memo wrapper) blocks re-renders of the card list during drag — this is the performance optimization from PR #15714. Previously, to work around this, the placeholder was placed outside the `innerRef` container, breaking drop zone detection. By lifting `innerRef` to the parent `StyledColumn`, both the memo'd cards and the placeholder live inside the `innerRef` DOM element, satisfying the library's requirements while preserving the performance optimization.
2026-03-23 07:47:55 +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%