Allow calendar names of infinite length.

[RokeJulianLockhart]

Is your feature request related to a problem? Please describe.

I use the calendar URIs as their names, because it's actually easier for me to parse since I have a lot of calendars. For instance, I want to add https://blackboard.ccn.ac.uk/webapps/calendar/calendarFeed/ee02e6834f124a7780cc809c3b6b7664/learn.ics (don't worry, I've randomized some characters) but must truncate it to https://blackboard.ccn.ac.uk/webapps/calendar/calendarFeed//learn.ics for Nextcloud to accept the name change.

Describe the solution you'd like

Allow me to add a calendar name of any length.

Describe alternatives you've considered

0. [ ] Allowing users to see added calendars' origin URIs in their detail panes as https://github.com/nextcloud/calendar/issues/5464#issue-1886032426 suggests
1. [ ] Presenting the calendars in a table view with the origin URIs as a visible attribute

Additional context

This isn't a problem when using https://github.com/Alinto/sogo at somewhere like https://mail.defencegateway.mod.uk/SOGo/so//Calendar/view.

[miaulalala]

Infinte length is going to be diffcult, as we also store the displayname in the db. I found nothing in the RFCs to limit the lenght of a displayname, so we're clear on that front; but I'm still unsure about interoperability. Google cuts off any displayname at 254 characters, no matter how long the string you post. This is our db limit too.

I would prefer to go with the other suggestion you made, to show the URL.

[tcitworld]

Also instead of showing the full URI we should consider the source of your issue: having a lot of calendars makes it hard to distinguish them. Other appropriate solutions would be to investigate calendar folders, allowing to filter the calendar list, etc.

[RokeJulianLockhart]

https://github.com/nextcloud/calendar/issues/5460#issuecomment-1711429110

@tcitworld, the sole alternative which would allow me to easily see the URIs in the list would be the aforestated

0. [ ] Presenting the calendars in a table view with the origin URIs as a visible attribute

which would mean that you'd need to implement something like

where I can reorganize the columns to show me the URI as the 1st field (at least when collapsed)

rather than the name. It would be incredible, but I doubt it'll occur, so this is probably the sole viable stopgap.

https://github.com/nextcloud/calendar/issues/5460#issuecomment-1711420512

Consequently, @miaulalala, that's not really an alternative. Honestly, I'm uncertain why I listed it as one.