Skip to content
New issue

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

Catch case where recurring item has no Start #322

Merged
merged 1 commit into from
Oct 17, 2017

Conversation

rbuehlma
Copy link
Contributor

In my case, the object without a Start was a TODO. The backend is Zimbra. I'm not sure if it is a Bug in Zimbra or if it is actually a valid item but the fix is simple in the library.

Copy link
Owner

@rianjs rianjs left a comment

Choose a reason for hiding this comment

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

Yeah, it looks like the only required property in VTODOs is the DTSTAMP:

https://tools.ietf.org/html/rfc5545#section-3.6.2

Can you make the same change in the .NET 2.x version as well in the v2 folder? Should be in the same place.

@rbuehlma
Copy link
Contributor Author

Sorry, missed the 2.x version again :-S done now.

Copy link
Owner

@rianjs rianjs left a comment

Choose a reason for hiding this comment

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

Cool. Two last things:

  • Can you edit the nuspec files in both the v2 and net-core versions and bump the patch version by 1?
  • Then add a short blurb to release-notes.md explaining the change with the associated major.minor.patch version. (You'll see what I mean when you open the file.) Something like "DTSTART is not required for VTODO components." would be sufficient.

Then I'll merge and publish new versions to nuget.

@rbuehlma
Copy link
Contributor Author

Done as well.

@rianjs rianjs merged commit 5e48855 into rianjs:master Oct 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants