Resolve interval handling when startAt set in the past #248
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
|
Thanks! Merging this into dev for inclusion in the next release |
buzzinJohnnyBoi
added a commit
to buzzinJohnnyBoi/croner
that referenced
this pull request
May 18, 2024
Hexagon
pushed a commit
that referenced
this pull request
May 18, 2024
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.
I updated the
/src/croner.js_nextfunction to calculate when the previous run time would be when theprev(previous run) isundefinedandstartAtandintervalare set.I also added 1 test to the
/src/suites/options.cjsfor this use case.I then ran
npm run buildto update thedist.Multiple packages in the
package-lock.jsonwere also updated as a result of runningnpm run buildFixes #247