avoid an exception raised when "start" is nil #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I got an exception when I created a schedule with 'cron' = ''. This is a valid schedule meaning that the query is not scheduled to run.
With this patch, create_schedule returns '' (empty string) when cron is ''. There might be a better value than ''. The API probably should return a Python object or JSON object instead of start time, but it breaks compatibility.