-
Notifications
You must be signed in to change notification settings - Fork 1
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
Support expressions in RRule
format
#25
Conversation
6c91b56
to
56694b9
Compare
efbaf6f
to
dbd9a25
Compare
95bacbb
to
c14a510
Compare
c14a510
to
53a554b
Compare
f591ad8
to
f5c2749
Compare
5bf80c5
to
1754206
Compare
1754206
to
75b9976
Compare
e39a49e
to
95b9171
Compare
95b9171
to
afe46d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use lower case in JSON and just use start
and end
without complicating things.
It's not something I chose to do. However, if you want me to do that all by myself, I can do it. But then, I have to convert everything back to uppercase in |
We handle start and end on our own so I don't see why we can't just serialize the following:
|
Also please move |
Yes, but only for the regular frequencies which don't have Lines 265 to 278 in afe46d9
|
Hadn't looked closely enough at how serialization and deserialization should work. I think there is no need to do anything with microseconds since iCalendar dates only work to the second. Also, I wouldn't test serialized JSON. This is an implementation detail: |
57b4c04
to
8875b83
Compare
8875b83
to
a8f41a8
Compare
a8f41a8
to
7a7966f
Compare
No description provided.