0439b96eca
This PR implements a new clean parallel code path for handling the filter manipulated in an object filter dropdown. Remember that the object filter dropdown module is the generic, shared module, that must be vertically implemented in those places : view bar filter button, record table column header cell, view bar details filter chip. So here we implement, just for the text filter input (for example a FULL_NAME field type), a new parallel code path logic, that runs on a new state : objectFilterDropdownCurrentRecordFilterState We still update the selectedFilter state, that is very close to the new objectFilterDropdownCurrentRecordFilterState, but in order to be cautious, and allow us to refactor incrementally, we implement a new parallel code path and let the rest run on selectedFilterState for now. The new way of working with the filter in the object filter dropdown, includes smaller and more specific hooks : - useApplyObjectFilterDropdownFilterValue instead of applyRecordFilter which API generates a lot of tech debt - useObjectFilterDropdownFilterValue to get the current value (might be later removed if too thin) - useUpsertObjectFilterDropdownCurrentFilter, to abstract a bit some duplicated logic in useApplyObjectFilterDropdownFilterValue - useCreateRecordFilterFromObjectFilterDropdownCurrentStates which differs from the existing useCreateEmptyRecordFilterFromFieldMetadataItem in that it uses the current states instead of creating an empty filter with default values. Those two logics are still very confusing and duplicated everywhere, creating specific hooks makes it clear now. This PR shouldn't cause any change in the behavior of the filtering feature. Fixes https://github.com/twentyhq/core-team-issues/issues/717
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!