5946b37712
This PR refactors the generic module object dropdown filter input. We have multiple components for each filter type and each one was using selectedFilterState and the applyRecordFilter hook to read and set its value. The main issue was that each component was forced to pass every property of a RecordFilter to applyRecordFilter to only modify the value property, thus creating a lot of unnecessary dependencies and tight coupling between every component and hook that used the record filters. Now we have each component only reading from a new objectFilterDropdownCurrentRecordFilterComponentState, scoped to a ObjectFilterDropdownComponentInstanceContext, thus whether we're in a view bar dropdown, an editable filter chip dropdown or an advanced filter dropdown, we know where to read the filter value from. This component state might even be simplified by only storing the record filter id, thus avoiding having to synchronize this state with its counterpart in currentRecordFilterComponentState, but we should try after the main refactor effort, as those two states aren't in the same instance context. We implement a new applyObjectFilterDropdownFilterValue hook to handle the value setting from an object filter dropdown input component. There's also a new useApplyObjectFilterDropdownOperand for doing the same but for operand. Another important thing that had to be done to keep a synchronous code path was to set the states of each advanced filter row at the advanced filter dropdown onOpen event, using useSetAdvancedFilterDropdownStates. Finally we remove : useApplyRecordFilter, useSelectFilterUsedInDropdown and selectedFilterComponentState which were making all of this zone difficult to work with. Closes https://github.com/twentyhq/core-team-issues/issues/718 Closes https://github.com/twentyhq/core-team-issues/issues/720
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See:
🚀 Self-hosting
🖥️ Local Setup
Does the world need another CRM?
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
We're currently developing Twenty's beta version.
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Add, filter, sort, edit, and track customers
- Create one or several opportunities for each company
- See rich notes tasks displayed in a timeline
- Create tasks on records
- Navigate quickly through the app using keyboard shortcuts and search
Add, filter, sort, edit, and track customers:
Create one or several opportunities for each company:
Track deals effortlessly with the email integration:
Tailor your data model to meet business needs:
See rich notes displayed in a timeline:
Create tasks on records
Navigate quickly through the app using keyboard shortcuts and search:
Connect your CRM to all your tools through our APIs and Webhooks.
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Recoil, Emotion 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!