Simon Ser

All right. Is there anything else to mount?

Related: https://github.com/emersion/go-webdav/issues/24

TBH, maybe we shouldn't do any of the quoting/unquoting stuff. It would be a bit awkward to deal with quoted strings, but at least we wouldn't have this kind of...

We've already made plenty of breaking changes since the last release.

Hm, this new proposal is error-prone. Library users need to "guess" that they need to double-quote the ETag values they're using. It's very easy to break the RFC with this...

`string(ao.ETag)` should work as well.

With your changes, the ETag contains quotes already, no need to add them again.

The idea looks good to me. Maybe we could instead change the `CalendarCompRequest` fields to be pointers, but not sure it's worth it.

Hmm. Actually, why is `CalendarCompRequest.Name` not set to `VCALENDAR`? [The RFC](https://tools.ietf.org/html/rfc4791#section-9.7.1) seems to indicate that `` MUST have a ``, and that `` MUST have a `name` attribute.

For reference, here's how I've been using `QueryCalendar`: https://git.sr.ht/~emersion/alps/tree/master/plugins/caldav/routes.go#L104 This package is in dire need of examples.