f7e2c1c627
If you tried to add a delay in `refreshObjectMetadataItems` like this` await new Promise((resolve) => setTimeout(resolve, 5000))`, then this caused an issue where the user was redirected to his workspace because the metadata was not loaded. This happened because I had removed the call to fetch metadata explicitly in useAuth (instead relying on the effect to fetch it because it was done twice). I had removed it because this was causing issues in the onboarding process where /metadata was called too early and then cached with the wrong reply. The correct fix is instead to change the fetch policy to `network only` to stop hiding re-renders to the object metadata effect with Apollo's cache mechanism. Now the [] reply isn't cached in the onboarding, the metadata effect is only triggered during initial page load and refresh should be called explicitely. I also noticed a bug on the server side where sometimes the frontend was passing a token for public requests (login token exchange request, public domain data request). I removed the check so that the backend completely ignores the token when it's passed on public request. The downside is that we're losing information for logs (who did that request to a public endpoint), but it doesn't make much sense to throw authentication errors on that endpoint imo. Probably a better root-cause fix would be to understand why a token is still passed on the frontend, but that would require more investigation — the bug happened when I was signing up and redirected from the app.xxx domain to the workspace domain
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!