feat(backoff)!: add configurable jitter modes - #283
Conversation
Replace the boolean jitter switch with explicit modes and align built-in backoff caps with the runtime timer limit.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fdaa98dd6c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a738c05655
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Let direct callers carry the effective previous delay and keep legacy Boolean configuration aliases during the enum migration.
Summary: replaces Boolean exponential jitter with explicit None, Equal, Full, and Decorrelated modes; adds jitter to constant and linear backoff; keeps decorrelated state execution-local and exposes a previous-delay overload for direct consumers; removes the hidden one-day cap; updates DI, HTTP configuration, Testing descriptors, docs, tests, and API ledgers. Legacy Boolean configuration values remain accepted. Breaking change for 1.0: the public Backoff factory signatures and Jitter metadata now use the Jitter enum. Closes #203. Validation: Release solution build; core, Testing, .NET Standard fallback, and allocation tests on supported frameworks; docs structure, compiled snippets, and production site build.