DTSTART seems not to be a native property for RRULE

[nilmerg]

https://icalendar.org/iCalendar-RFC-5545/3-8-5-3-recurrence-rule.html only speaks of DTSTART when not directly referring to the RRULE properties. The examples shown also don't show it as such.

rrule.js seems to be able to cope with it, but I'd not be surprised if another library cannot. @yhabteab Please check if that's the case with the library you're using in the newest go project 😉

[nilmerg]

We've discussed this offline and the result is:

• DTSTART must not be part of the RRULE definition when exporting using jsonSerialize()
  • It should be a separate entry in the array alongside rrule instead
• This is because the go library we use doesn't support that property once a timezone is defined
• The php library also has a problem with such

[nilmerg]

I'd suggest to store the start as start in DateTimeInterface::ATOM format. Once outside the RRULE it doesn't have any meaning and thus the DTSTART name is meaningless.

[yhabteab]

I'd suggest to store the start as start in DateTimeInterface::ATOM format.

Why? We have introduced our own format last time.

[nilmerg]

Ah, nvm, didn't remember this.