Sonarly Claude Code
5b1810d62e
https://sonarly.com/issue/15272?type=bug The findMany and aggregate record queries both write to the same `Query.companies` cache key with incompatible `CompanyConnection` shapes, causing Apollo Client to overwrite one result with the other and producing undefined data access errors. Fix: Added a GraphQL alias to aggregate queries to prevent Apollo cache collisions with findMany queries. **Problem:** Both `useFindManyRecords` and `useAggregateRecords` issue GraphQL queries targeting the same field (e.g., `Query.companies`). In Apollo Client v4, these results collide in the cache — the aggregate result `{percentageEmptyLinkedinLink: 1}` overwrites the findMany result `{edges: [...], pageInfo: {...}, totalCount: 45}` (or vice versa), producing `undefined` data reads that trigger the TypeError. **Fix:** The aggregate query now uses a GraphQL alias (`aggregate_companies: companies(filter: $filter)` instead of `companies(filter: $filter)`). This causes Apollo to store the aggregate result under a different cache key (`Query.aggregate_companies`) than the findMany result (`Query.companies`), eliminating the collision entirely. **Changes:** 1. `generateAggregateQuery.ts` — Added `getAggregateQueryAlias()` helper and applied the alias in the generated query 2. `useAggregateRecords.ts` — Updated data access to read from the aliased key instead of `objectMetadataItem.namePlural` 3. Test files updated to match new query shape and mock response structure The GraphQL operation name (`AggregateCompanies`) is unchanged, so `useRefetchAggregateQueries` continues to work without modification.
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!