8b5eb04b07
## Context We would like to start leveraging more messageFolders during messageSync which would allow users to select folders they want to sync on their mailbox. MessageFolder is an abstraction that means folder for Microsoft, labels for Gmail, not supported for IMAP. ## What 1) We do not aim to build a FE now but we would like to take it into a consideration if they have been modified through API. So **out of scope** 2) MessageFolders will be synced regularly from Gmail, Microsoft. This is currently partially done and improving it is **out of scope** 3) Change: we were having two synchronization mechanism so far: FULL_SYNC (first time, or when no cursor is present) and PARTIAL_SYNC (when we have a cursor, we can fetch the diff since the last pull). This Full vs Partial mode was a high level concept. We now think it's an driver implementation detail (and can be inferred from the existence of a cursor). Why making this change now: as we are trying to pull several folders, a folder could need a full sync if it had no cursor, and another a partial if it has one. It does not make sense anymore to have this full vs partial difference at MessageChannel level 4) Once we are sure this work, we can start syncing different folders on Gmail side (the case for the user it to be able to fetch Promotion label) ## Implementation strategy 1) Re-use PartialMessageList implementation / API and rename it to MessageList at it's more complete 2) re-use driver level fullMessageList methods and call them messageListWithoutCursor 3) make sure that these method are folder specific ## Tests ### Gmail - Fresh fetch (without cursor): OK - Message import: OK - Additional fetch (with messageChannel cursor): OK ### Microsoft - Fresh fetch (without cursor): OK - Message import: OK - Additional fetch (with messageChannel cursor): OK ### Imap - Fresh fetch (without cursor): OK - Message import: OK - Additional fetch (with messageChannel cursor): OK
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
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 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!