Sonarly Claude Code
575e83c292
https://sonarly.com/issue/29531?type=bug SidePanelPageLayoutRecordPageWidgetTypeSelect crashes during render when both `pageLayoutEditingWidgetId` and `widgetCreationTargetTabId` are null. This occurs because the Replace Widget and Add Widget Above/Below navigation paths never set `widgetCreationTargetTabId` as a fallback, and `pageLayoutEditingWidgetId` can be independently cleared by auth-triggered re-renders or edit mode toggling. Fix: Changed `resolveWidgetTypeSelectTargetTabId` to return `null` instead of throwing when it encounters invalid state (both `pageLayoutEditingWidgetId` and `widgetCreationTargetTabId` are null, or the editing widget isn't found in any tab). This converts an unrecoverable render-time crash into a recoverable state. In `SidePanelPageLayoutRecordPageWidgetTypeSelect`: 1. Added `useEffect` that calls `closeSidePanelMenu()` when `tabId` is null — this gracefully closes the side panel when state becomes inconsistent (e.g. after auth token renewal resets `pageLayoutEditingWidgetId`). 2. Added early `return null` after all hooks when `tabId` is null, preventing the component from rendering with invalid state. 3. Added `!isDefined(tabId)` guards at the top of all 4 `useCallback` handlers (`removeExistingWidgetIfReplacing`, `handleCreateFieldsWidget`, `handleCreateFieldWidget`, `handleCreateFrontComponentWidget`) to ensure TypeScript type safety and prevent operations with a null tab ID. Updated the existing test file to expect `null` returns instead of thrown errors for the two edge cases. The fix does not change behavior for any valid navigation path — `resolveWidgetTypeSelectTargetTabId` still returns the correct tab ID when state is properly set. It only adds graceful degradation for the race condition where external state resets (auth renewal, edit mode toggling) clear `pageLayoutEditingWidgetId` while the widget type select page is still on the side panel navigation stack.
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