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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Docs] Add clarification about property precedence #1918
[Docs] Add clarification about property precedence #1918
Changes from 1 commit
f7b6a6c
a79988d
106df37
9345f5f
a1515c8
4607b93
aef2b88
eb4b475
d28bd3e
027c732
1e71491
7ad36e0
4614dcb
dfbfb3d
62665fa
8cf291a
e39d09c
622cecc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering, shall we apply the capping to values produced by generator too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say yes. That was my intuition before I checked the implementation. But let's deal with that in a separate PR if you don't mind.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My intuition says yes too, the less special cases, the better. The only downside is that sometimes the
Retry-After
won't be fully respected if the value is greater thanMaxDelay
.https://github.com/dotnet/extensions/blob/9f25d9d74674483298cd167cf8ff6e9d9026bf20/src/Libraries/Microsoft.Extensions.Http.Resilience/Polly/HttpRetryStrategyOptions.cs#L57
Thoughts @martincostello
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would agree we should apply it -
Retry-After
isn't necessarily authoritative and the user may wish to try earlier by overriding. If we do that we should make it clear in the documentation.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a concision decision by the strategy configurator that (s)he sets the
MaxDelay
. If it is set then the strategy should cap the value regardless how it is calculated/retrieved IMHO.Check failure on line 342 in docs/strategies/retry.md
GitHub Actions / publish-docs
Emphasis style
Check failure on line 342 in docs/strategies/retry.md
GitHub Actions / publish-docs
Emphasis style
Check failure on line 342 in docs/strategies/retry.md
GitHub Actions / publish-docs
Emphasis style
Check failure on line 342 in docs/strategies/retry.md
GitHub Actions / publish-docs
Emphasis style