Fix sequence and wording of Rate Limiter in HttpStandardResilienceOptions

Open Beginner friendly
#11,760 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp
Domain
documentation

Research direction

Open xml/Microsoft.Extensions.Http.Resilience/HttpStandardResilienceOptions.xml and locate the Remarks list for HttpStandardResilienceOptions. Compare it with the linked standard-resilience-handler-defaults documentation and sequence diagram, then move Bulkhead to item 1 and rename it Rate Limiter. Done means the order and terminology are consistent with those references.

Written by the indexing model from the issue text.

Description

area-Extensions-HttpClientFactory untriaged
Type of issue

Typo

Description

Hi Maintainers,

In Remarks Bulkhead Item 3 in the numbered list should be moved up to Item 1 to match the sequence diagram and the documentation in standard-resilience-handler-defaults.

Also suggest renaming Bulkhead to Rate Limiter to match whats documented in Properties and standard-resilience-handler-defaults for consistency.

Thanks

Page URL

https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.http.resilience.httpstandardresilienceoptions?view=net-9.0-pp

Content source URL

https://github.com/dotnet/dotnet-api-docs/blob/main/xml/Microsoft.Extensions.Http.Resilience/HttpStandardResilienceOptions.xml

Document Version Independent Id

55fcbac1-6729-6905-16c0-b02ea8a652e0

Platform Id

16624a15-863b-d552-8de3-4e9de0ffba5a

Article author

@dotnet-bot

Dominant language
C#
Stars
950
Forks
1.7k
Avg merge
3d 5h
Merged PRs (30d)
38

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/dotnet-api-docs

All issues in dotnet/dotnet-api-docs

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.