0238d8bd53
https://sonarly.com/issue/23699?type=bug After saving view filters/sorts, the local metadata store is not updated optimistically — it waits for an asynchronous SSE event round-trip from the backend, causing the "Update view" button to remain visible and requiring a second click. Fix: After each view save hook's mutations succeed, the metadata store (`metadataStoreState`) is now optimistically updated to reflect the new state immediately. This eliminates the dependency on the SSE round-trip for UI state reconciliation. **What changed in each file:** 1. **`useSaveRecordFiltersToViewFilters.ts`** — After all create/update/delete filter mutations succeed, replaces the `viewFilters` entries in `metadataStoreState.current` for the current view with the computed `newViewFilters`. 2. **`useSaveRecordSortsToViewSorts.ts`** — Same pattern for `viewSorts` entries. 3. **`useSaveRecordFilterGroupsToViewFilterGroups.ts`** — Same pattern for `viewFilterGroups` entries. 4. **`useSaveAnyFieldFilterToView.ts`** — After the view update mutation succeeds, updates the `anyFieldFilterValue` field on the current view in the `views` metadata store entry. Each optimistic update: - Reads the current state from the metadata store (respecting draft-pending status) - Filters out entries belonging to the current view - Replaces them with the new computed values - Writes directly to `.current` so the `viewsSelector` (which reads `.current`) immediately reflects the saved state When the SSE event arrives later, the `addToDraft`/`applyChanges` pipeline will find the data already matches and skip unnecessary updates due to `isDeeplyEqual` checks. |
||
|---|---|---|
| .claude-pr | ||
| .cursor | ||
| .github | ||
| .vscode | ||
| .yarn | ||
| packages | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .mcp.json | ||
| .nvmrc | ||
| .yarnrc.yml | ||
| CLAUDE.md | ||
| jest.preset.js | ||
| LICENSE | ||
| nx.json | ||
| package.json | ||
| README.md | ||
| tsconfig.base.json | ||
| yarn.config.cjs | ||
| yarn.lock | ||
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!