Add support for a .Delay(x) for recurrent jobs #16
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.
In ocassions we want to add some delay to a recurrent job that is different to the recurrent period itself.
I add a
.Delay()
modifier that changes the time for the initial delay. Thisin incompatible to
NotImmediatelly()
.I added here two possible implementation in two different commits:
.Delay(10 * time.Second)
: we pass atime.Duration
directly.Delay(10).Seconds()
: more complex and magic behaviour, it behaveslike
Every(x)
, but nicer to readLet me know which one you like the most and I can rebase this PR (or just merge it if you like it :))