Skip to content
This repository was archived by the owner on Jun 9, 2025. It is now read-only.

Conversation

@rfc2822
Copy link
Member

@rfc2822 rfc2822 commented Mar 28, 2024

…LocalDate and LocalTime instead of modifying the original value on the fly

…LocalDate and LocalTime instead of modifying the original value on the fly
@rfc2822 rfc2822 self-assigned this Mar 28, 2024
@rfc2822 rfc2822 added the bug Something isn't working label Mar 28, 2024
@rfc2822 rfc2822 requested a review from sunkup March 28, 2024 09:36
@rfc2822 rfc2822 marked this pull request as ready for review March 28, 2024 09:37
Copy link
Member

@sunkup sunkup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me :)

@rfc2822 rfc2822 merged commit f10bd57 into main Mar 28, 2024
@rfc2822 rfc2822 deleted the 147-getting-invalid-date-april-31-when-specification-of-time-for-exdate-is-missing branch March 28, 2024 11:23
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Getting "Invalid date 'APRIL 31'" when specification of time for EXDATE is missing

2 participants