nextcloud / nextcloud/integration_davc
Segment VTODO and VJOURNAL collections out (until supported)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 12
- Forks
- 2
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 16
Description
Current behavior:
Integration_davc lists every discovered iCalendar collections under:
i) Personal Settings /Connected accounts and
ii) the side bar of the Calendar app.
These include pure task lists (VTODO) and journals (VJOURNAL), presumably because all share the iCalendar spec.
Task and journal collections clutter the calendar view and render nothing useful there.
DAV task collections to my knowledge are not (yet?) supported by NC Tasks app.
DAV Journals are a widespread gap, as JTX is one of the only clients that manages them well.
Address books are nicely in a section of the Connected accounts Personal Settings page, and do not display except in the NC Contacts app.
The component type is already known to DAVC at discovery (the type column distinguishes them).
Request:
Sort the collection's component type in the Connected accounts settings, similar to how Address Books are separated from Calendars (for iCal collections of different types, could be in columns).
To the Calendar app, expose only VEVENT collections, not VTODOs or VJOURNALs, so only true VEVENT calendars are listed in the app side bar/panel.
Bonus: expose VTODO collections to the Tasks app
Super Bonus: expose VJOURNAL to Notes App.
Environment: Nextcloud 33.0.3, integration_davc 1.0.4, Radicale 3.7.4.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how integration_davc discovers collections and uses the existing type column, then inspect the Connected accounts settings and Calendar app sidebar consumers. Done means separating collection types in settings and exposing only VEVENT collections to Calendar; the optional Tasks and Notes integrations are additional scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100