fix(calendar): correct ICS event formatting and time zone usage #16009
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 <[email protected]>
Author
|
@alperozturk96 Review and merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.