fix(calendar): correct ICS event formatting and time zone usage #16009
Conversation
|
@alperozturk96 Review and merge |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
The ICS event file has been updated to follow proper RFC 5545 formatting. Changes: - Added a valid DESCRIPTION field instead of an empty one - Unified DTSTART and DTEND to use the same TZID (Europe/Berlin) - Ensured the event duration is correct and consistent - Cleaned up extra blank lines to avoid parsing issues - Retained the complete VTIMEZONE block for compatibility with Nextcloud, Google Calendar, and iOS This improves interoperability with calendar clients and prevents parsing errors caused by mixed time formats. Signed-off-by: Gorlesunilkumar <g2005.sunil2005@gmail.com>
AndyScherzinger
force-pushed
the
patch-1
branch
from
8194295 to
ae16c73
Compare
3 participants
The ICS event file has been updated to follow proper RFC 5545 formatting and improve compatibility with calendar applications.
Changes
Why
These adjustments improve interoperability with various calendar clients and prevent potential parsing issues caused by mixed time formats or empty fields.
Testing
The change updates only static test assets. No functional logic was modified.