Sonarly Claude Code
dfc0a4d5fc
https://sonarly.com/issue/29560?type=bug
The `findManyApplications` GraphQL query fails when a client requests `applicationVariables` (or any of 4 other OneToMany relation fields), because the backend no longer loads those relations but the GraphQL schema still declares them as non-nullable.
Fix: The root cause is a schema-reality mismatch introduced by commit 9a95cd02ed (PR #19892, merged 2026-04-20). That PR intentionally removed OneToMany relation loading from `findManyApplications` to fix Cartesian product timeout issues, but neglected to update the GraphQL schema. Five `@Field()` decorators on ApplicationDTO declared OneToMany relation fields (agents, frontComponents, logicFunctions, objects, applicationVariables) as non-nullable, but multiple code paths return ApplicationDTO instances without those fields populated.
The fix adds `{ nullable: true }` to all five `@Field()` decorators, making the GraphQL schema accurately reflect that these fields are optionally loaded. This is consistent with the TypeScript type annotations (all five properties already had `?` optional markers) and with the existing pattern used by other optional fields in the same DTO (e.g., defaultLogicFunctionRole, applicationRegistration).
This resolves the Sentry error "Cannot return null for non-nullable field Application.applicationVariables" and prevents the same class of error for the other four relation fields. The fix is safe because: (1) the standard frontend FIND_MANY_APPLICATIONS query doesn't request these fields, (2) the frontend FIND_ONE_APPLICATION query does request them but that code path (findOneApplication) properly loads all relations via Promise.all, and (3) any third-party API consumers or SDK users will now get null instead of a hard GraphQL error when these fields aren't loaded.
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