-
Notifications
You must be signed in to change notification settings - Fork 2
fix broken DTSTART value type for DATE values #5
Comments
We don't touch DTSTART entries anymore. If this is still valid (and I can see some of that in my files...) then it's a bug in what generates the original ics bits in the mails (likely groupwise). So WONTFIX for us :/ |
Why WONTFIX? Wouldn't it be worth working around Groupwise brokenness, given that's the main use case for us? |
Does it actually break anything for you? If yes, then okay, I can add the workaround. But if not, then I'd prefer to not have to deal with it since I don't want to accumulate unneeded workarounds in there. |
I would have thought it did, otherwise there would be no good reason for me to report it ... but I can't remember what. |
The default value type is DATE-TIME, so when a DATE is used, the value type has to be specified. Closes #5.
@aspiers ah well. I've added the workaround for now. I do have events with that bug, and it didn't impact me, fwiw. |
Thanks! :) |
Thinking about this a bit more, I guess it would break all-day events, but ICBW. |
Lines like
are invalid, because
20140612
is aDATE
value type, whereasDTSTART
's default value type isDATE-TIME
.http://icalvalid.cloudapp.net/ says
but actually section 3.8.2.4. of the RFC is far more informative about this.
The text was updated successfully, but these errors were encountered: