747519377b
https://sonarly.com/issue/25062?type=bug Application configuration variables on the Settings page use an unreliable 250ms debounced auto-save pattern with no user feedback, causing users to lose input values when navigating away or when the component re-renders. Fix: Replaced the unreliable 250ms debounced auto-save pattern with explicit per-variable Save buttons, matching the team's established pattern from `SettingsApplicationRegistrationGeneralTab`. **Changes to `SettingsApplicationDetailEnvironmentVariablesTable.tsx`:** - Removed `useDebouncedCallback` and the auto-save-on-keystroke behavior - Changed prop from `onUpdate` (fire-and-forget) to `onSave` (async with Promise) - Added per-variable Save button (IconCheck) that is disabled until the input has a non-empty value - Input fields now use `placeholder` to show the current server value instead of pre-filling the input (prevents masked secret values from becoming editable content) - Added `savingKeys` state to disable buttons during save operations - On successful save, the edited value is cleared (input returns to placeholder state) **Changes to `SettingsApplicationDetailSettingsTab.tsx`:** - Added `useSnackBar` for success/error feedback on save - Added `useApolloClient` to refetch `FindOneApplicationDocument` after mutation, keeping the Apollo cache in sync - Changed from `onUpdate` to `onSave` prop, wrapping the mutation with try/catch for error handling - Shows success toast "Variable {key} updated" on save, error toast on failure |
||
|---|---|---|
| .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!