Sonarly Claude Code
4a7d644e82
https://sonarly.com/issue/7468?type=bug The `upsertWorkspaceFeatureFlag` method uses a non-atomic find-then-save pattern instead of a database-level upsert, causing duplicate key violations under concurrent requests. Fix: Replaced the non-atomic find-then-save pattern in `upsertWorkspaceFeatureFlag` with a database-level `upsert` using `conflictPaths: ['workspaceId', 'key']`, followed by `findOneOrFail` to retrieve the full entity for the return value. **Why this approach:** The original commit `9883472d55c` deliberately switched from `upsert` to find/save because TypeORM's `upsert` doesn't reliably return all entity fields. The fix preserves the intent (returning a complete entity) while restoring atomicity by splitting into two steps: an atomic upsert (handles the race condition), then a find (returns the full entity). This is the same pattern already used by `enableFeatureFlags` (line 66) in the same file, making it consistent with existing code. **Changes:** 1. **`feature-flag.service.ts`** — Replaced `findOne` → conditional build → `save` with `upsert` → `findOneOrFail` 2. **`feature-flag.service.spec.ts`** — Updated mock repository to include `findOneOrFail`, updated test assertions to verify `upsert` and `findOneOrFail` calls instead of `save`
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
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
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- 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
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!