Typo fix in Backoff.exponential/2 documentation #964
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
Replace millseconds with seconds wording to avoid confusion
|
Thanks for the fix! Accuracy is always welcome, even for a private module 🙂 |
sorentwo
pushed a commit
that referenced
this pull request
Oct 26, 2023
Replace millseconds with seconds wording to avoid confusion
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.
Currently
Oban.Backoff.exponential/2function documentation refers that function calculates backoff inmillsecondswhich is not true, as Engine expects to receive backoff in seconds.This typo introduces confusion in understanding of how
Job.scheduled_attimestamp is calculated.