f6d0219838
https://sonarly.com/issue/29316?type=bug CalDAV connection testing catches all errors (discovery failures, missing homeUrl, no VEVENT calendars) and reports them as "Invalid CALDAV credentials," blocking users of standard-compliant self-hosted CalDAV servers from connecting despite valid credentials. Fix: Changed the CalDAV connection test error handler in `testCaldavConnection()` to properly classify errors instead of mapping all non-socket/non-sync errors to "invalid credentials": 1. **Added `"Invalid credentials"` check** (line 168-172): Only tsdav's actual 401-based auth error now shows the "invalid credentials" user message. This is the exact string tsdav throws when the server returns HTTP 401. 2. **Added CalDAV discovery error check** (lines 174-182): Discovery failures (`"cannot find homeUrl"`, `"cannot find calendarUserAddresses"`, `"No calendar with event support found"`) now get an accurate message: "We couldn't discover calendars on your CalDAV server. Please verify your server URL is correct and that your server supports CalDAV calendar discovery." These are the errors self-hosted servers (Baikal, Radicale) trigger when tsdav's PROPFIND-based discovery can't parse their responses. 3. **Changed the catch-all fallback** (lines 184-186): Unknown errors now get a generic "We encountered an issue connecting to your CalDAV server" message (matching the IMAP handler pattern) instead of blaming credentials. The error message strings come from the team's own `parse-caldav-error.util.ts` which already catalogs known tsdav errors. |
||
|---|---|---|
| .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
Why Twenty
Twenty gives technical teams the building blocks for a custom CRM that meets complex business needs and quickly adapts as the business evolves. Twenty is the CRM you build, ship, and version like the rest of your stack.
Learn more about why we built Twenty
Installation
Cloud
The fastest way to get started. Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date.
Build an app
Scaffold a new app with the Twenty CLI:
npx create-twenty-app my-app
Define objects, fields, and views as code:
import { defineObject, FieldType } from 'twenty-sdk/define';
export default defineObject({
nameSingular: 'deal',
namePlural: 'deals',
labelSingular: 'Deal',
labelPlural: 'Deals',
fields: [
{ name: 'name', label: 'Name', type: FieldType.TEXT },
{ name: 'amount', label: 'Amount', type: FieldType.CURRENCY },
{ name: 'closeDate', label: 'Close Date', type: FieldType.DATE_TIME },
],
});
Then ship it to your workspace:
npx twenty deploy
See the app development guide for objects, views, agents, and logic functions.
Self-hosting
Run Twenty on your own infrastructure with Docker Compose, or contribute locally via the local setup guide.
Everything you need
Twenty gives you the building blocks of a modern CRM (objects, views, workflows, and agents) and lets you extend them as code. Here's a tour of what's in the box.
Want to go deeper? Read the 
User Guide for product walkthroughs, or the Documentation for developer reference.
|
|
|
|
|
|
Learn more about version control in docStack
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 · Discord · 
Feature requests · Releases · 
X · 
LinkedIn · 
Crowdin · 
Contribute