Skip to content

Support for username property for ical#68

Open
mbartel wants to merge 1 commit into
thunderbird:mainfrom
mbartel:usernameSupportForCalDav
Open

Support for username property for ical#68
mbartel wants to merge 1 commit into
thunderbird:mainfrom
mbartel:usernameSupportForCalDav

Conversation

@mbartel
Copy link
Copy Markdown

@mbartel mbartel commented Apr 18, 2026

Implemented support for "username" property needed by CalDav for the username field in the UI

@mbartel mbartel requested a review from kewisch as a code owner April 18, 2026 15:06
Comment on lines +72 to +75
if (username && username != calendar.getProperty("username")) {
matches = false;
}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should gate being able to query by username behind some sort of permission. Maybe accountsRead?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jobisoft Thoughts on this? Am I being too cautious?

"showReminders": { "type": "boolean" },
"color": { "type": "string", "optional": true },
"capabilities": { "$ref": "CalendarCapabilities", "optional": true }
"capabilities": { "$ref": "CalendarCapabilities", "optional": true },
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the original patch for the username addition, it appears there is also a capability for usernames. Maybe we should add it to CalendarCapabilities and add a check in the provider code while we're at it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants