-
Notifications
You must be signed in to change notification settings - Fork 95
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
Extended schedules #729
Extended schedules #729
Conversation
Codecov Report
@@ Coverage Diff @@
## master #729 +/- ##
=========================================
+ Coverage 5.65% 5.66% +<.01%
=========================================
Files 767 768 +1
Lines 25303 25351 +48
Branches 5716 5722 +6
=========================================
+ Hits 1431 1435 +4
- Misses 21454 21485 +31
- Partials 2418 2431 +13
Continue to review full report at Codecov.
|
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.
The "Edit Schedule" dialog is sending the "create_schedule" command instead of "save_schedule".
There duration is also wrong if it's set to zero but that looks like something I should check in gvmd.
The icalendar param must contain VCALENDAR data.
When creating a new schedule expect a icalendar parameter.
All ical related code is moved to an extra model module.
Support icalendar data when creating a new schedule instead of the legacy year, hour, duration, ... parameters.
No functionality of the ScheduleDialog has been changed yet. It just supports converting the current data into the icalendar format.
When calling save_schedule command use the icalendar param and forward it to gvmd.
When saving the a Schedule use the icalendar data.
Forward the id to the onSave handler to be able to decide if saving is a create or modify/save command.
Part 3
Support creating Schedules via icalendar (https://tools.ietf.org/html/rfc5545) data