empty list value for Schedule fields is undefined #407
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.
The Schedule annotation does not define what to do when fields (such as
months
orhours
) are assigned a value of empty list.One option could be for empty to indicate that it should run at no hours or no months, but that would be pointless to use the annotation at all in that case.
Or empty could raise an error.
Or another option would be for empty to indicate that the field is disregarded entirely, effectively being able to run at all of the values. This seems the most useful because it could be more convenient than listing all of the possible values.
The pull updates the JavaDoc to define the behavior as the latter. Also, I noticed the JavaDoc for these methods was difficult to read with everything in a single paragraph, so I split it up into paragraphs.