fix: Allow Leading Zeroes in Cron #116
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n cron (ex: 02 will interpret as february)
|
This pull request has been linked to Shortcut Story #8620: Supercronic doesn't evaluate "fake" dates (i.e. Feb 31st) properly. |
UserNotFound
approved these changes
Feb 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
interpret leading zeroes for the month field correctly (ex: 02 will interpret as february), previously the behavior was not intuitive as
"11 1 31 03 *"would evaluate to 2023-12-31 01:11:00 instead of 2023-03-31 01:11:00