Timezone property parameter encoding
allenporter opened this issue · 2 comments
Is your feature request related to a problem? Please describe.
At the moment the TZID handling just uses python timezones. However, the rfc states that they should reference an existing
timezone component. Basically the tzid parameter is entirely ignored when round tripping back to storage e.g.:
- DTSTART;TZID=America/Los_Angeles:20220802T090000
- DTEND;TZID=America/Los_Angeles:20220802T093000
+ DTSTART:20220802T090000Z
+ DTEND:20220802T093000Z
This needs to be solved: Do we take a stance not to use timezones at all? or hack it with python timezones still? Unclear.
Need to also make sure this works for all components that have timezones and do custom encoding. May require generalization of the json encoding and post json encoding.
Timezone property parameters are now fully supported. Using an EventStore will manage automatically handling Timezone components to the calendar based on any new events that are added.