Sonarly Claude Code
233f7a7d17
https://sonarly.com/issue/24634?type=bug A relative date filter value stored in JSON format (`{"unit":"DAY","amount":7,"direction":"NEXT"}`) cannot be parsed by the regex-based `relativeDateFilterStringifiedSchema` which expects the format `NEXT_7_DAY;;timezone;;`, causing a crash on the /objects/meetings page when resolving view filters into GraphQL operation filters. Fix: Three changes fix both the source of bad data and handle existing bad data: 1. **WorkflowStepFilterValueInput.tsx (line 111)**: Changed `JSON.stringify(newRelativeDateFilter)` to `stringifyRelativeDateFilter(newRelativeDateFilter)`. This ensures new workflow step filter values are serialized in the expected regex-stringified format (`NEXT_7_DAY;;timezone;;`) instead of raw JSON. The import was already present on line 12. 2. **resolveRelativeDateTimeFilterStringified.ts**: Added `safeParseRelativeDateFilterJSONStringified` as a fallback when the regex-based `relativeDateFilterStringifiedSchema.safeParse()` fails. This handles existing JSON-format values already persisted in user view filters without breaking the primary parsing path. 3. **resolveRelativeDateFilterStringified.ts**: Same fallback added to the DATE variant (sibling of the DATE_TIME resolver) for consistency, since it has the same vulnerability. 4. **Test file**: Added two test cases verifying that both resolvers correctly handle JSON-stringified filter values as fallback input. The `safeParseRelativeDateFilterJSONStringified` utility already existed in twenty-shared and uses Zod schema validation, so the fallback is safe and well-validated.
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!