Sonarly Claude Code
2df52785ba
https://sonarly.com/issue/36114?type=bug Users who attempt to duplicate an incomplete workflow (one with steps but no trigger configured) receive an unhandled error. The backend strictly requires a trigger to be present in the source version before duplication, but the frontend offers the duplicate action regardless of whether a trigger exists. Fix: ## Code fix: `workflow-version.workspace-service.ts` Removed `assertWorkflowVersionTriggerIsDefined(sourceVersion)` and `assertWorkflowVersionHasSteps(sourceVersion)` from the `duplicateWorkflow` method. These guards are appropriate for *activating* a workflow (handled in `workflow-trigger.workspace-service.ts`) but not for duplicating one — a duplication always produces a new DRAFT, so copying an incomplete draft (missing trigger or steps) into another draft is semantically valid and was already handled correctly by the surrounding code: - `sourceVersion.trigger` null → `remappedTrigger = undefined` (already guarded with `isDefined(newTrigger)`) - `sourceVersion.steps` null/empty → `for (const step of sourceVersion.steps ?? [])` (already guarded with `?? []`) The imports for both utilities are preserved because they continue to be used in `createDraftFromWorkflowVersion`. ## Monitoring fix: `workflow-version.resolver.ts` Added `WorkflowTriggerGraphqlApiExceptionFilter` to the `@UseFilters` decorator on `WorkflowVersionResolver`. This filter converts `WorkflowTriggerException` into a `UserInputError` (a GraphQL-level validation error), which prevents it from being sent to Sentry. This matches the existing pattern in `workflow-builder.resolver.ts` and `workflow-trigger.resolver.ts`, which already apply this filter. Without it, any future `WorkflowTriggerException` thrown from `createDraftFromWorkflowVersion` or `updateWorkflowVersionPositions` would also produce noisy Sentry events.
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