Sonarly Claude Code
fff0667c9b
https://sonarly.com/issue/31631?type=bug
The "Navigate to next/previous record" command throws an unhandled error when the user clicks the navigation button before the current record's data has been loaded into the Jotai record store, resulting in an error snackbar and a failed navigation.
Fix: Changed `throw new Error(...)` to `return null` in both `NavigateToNextRecordSingleRecordCommand` and `NavigateToPreviousRecordSingleRecordCommand`.
**Why:** When the user rapidly clicks "Navigate to next/previous Person" after navigating to a new record page (especially during auth token renewal), the record data may not yet be loaded into `recordStoreFamilyState`. The `buildHeadlessCommandContextApi` reads the record store synchronously — if the record hasn't been loaded via GraphQL yet, `recordStoreFamilyState.atomFamily(id)` returns `null`, which gets filtered out by `isDefined`, leaving `selectedRecords` empty. The component then hits the guard and throws.
Throwing is the wrong behavior here because:
1. The error boundary (`CommandMenuItemErrorBoundary`) catches it, renders `null` as fallback, and shows an error snackbar to the user — but the error isn't actionable by the user
2. It fires a Sentry event for what is actually a transient data-loading race condition, not a true application error
3. The sibling command `SeeVersionWorkflowRunSingleRecordCommand` already uses `return null` for the same scenario (established in commit 6ce23a4115)
Returning `null` makes the command a silent no-op when data isn't ready, avoiding the error snackbar and Sentry noise. The `HeadlessEngineCommandWrapperEffect` that would have been rendered will simply not execute, and the user can retry the navigation once the page fully loads.
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