nextcloud / nextcloud/calendar
Hiding calendars in public shares
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Is your feature request related to a problem? Please describe.
Hi everyone!
After updating the calendar app recently, I just noticed that it is not possible to change the visibility of calendars in public shares any more, due to this commit.
This is quite unfavorable: We are sharing a total of six calendars in a single link to a broader public (definitively no tech folks - they need it as easy as possible!). Each calendar contains the events for a particular location in our region. Of course, the calendars are public and only a few users have an NC account to add/edit events.
Because most of the users will only be interested in the events for individual locations + a "general" calendar (and displaying all of the events would be very confusing), we always gave the hint to hide the calendars that are not of interest. Now this is not possible anymore!
Because of that, I would like to ask: What is wrong about providing this feature in public shares just because it cannot be persisted? It still can be useful for public users!
Are there any chances that you could bring back this feature? I think it is quite a "downgrade"...
Thank you!
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
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 reviewing commit 8fb5f9743f507f5d8679e77571fd3268e472945f and the public-share calendar interface it changed. Determine how calendar visibility is handled there; done means public users can hide or show individual calendars in a shared link without requiring the preference to be persisted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100