We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First of all, thank you for your great package.
Implementing your package at a customer leads to the issue, that handling with Events having only a start time, but no end time set, is not possible.
I first used next midnight to solve this, but customer only wants the start time and date set for these events.
I checked a corresponding event in the iCal validator and having an event only set with a DTSTART is a valid behaviour.
DTSTART
In your package the only class adopting this case, is TimeSpan, which needs to be begin and end set as DateTime.
TimeSpan
DateTime
Expected behaviour
Allow TimeSpan creation with only start set.
start
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
First of all, thank you for your great package.
Implementing your package at a customer leads to the issue, that handling with Events having only a start time, but no end time set, is not possible.
I first used next midnight to solve this, but customer only wants the start time and date set for these events.
I checked a corresponding event in the iCal validator and having an event only set with a
DTSTART
is a valid behaviour.In your package the only class adopting this case, is
TimeSpan
, which needs to be begin and end set asDateTime
.Expected behaviour
Allow TimeSpan creation with only
start
set.The text was updated successfully, but these errors were encountered: