Skip to content

docs: dispose registry which contains rate limiters#2438

Closed
lonix1 wants to merge 1 commit intoApp-vNext:mainfrom
lonix1:patch-1
Closed

docs: dispose registry which contains rate limiters#2438
lonix1 wants to merge 1 commit intoApp-vNext:mainfrom
lonix1:patch-1

Conversation

@lonix1
Copy link

@lonix1 lonix1 commented Jan 10, 2025

Pull Request

The issue or feature being addressed

Disposal docs

Details on the issue fix or feature implementation

See #2425

Confirm the following

  • I started this PR by branching from the head of the default branch
  • I have targeted the PR to merge into the default branch
  • I have included unit tests for the issue/feature
  • I have successfully run a local build

I'm not a GitHub expert, so I hope I did it properly!

@peter-csala
Copy link
Contributor

Hey @lonix1 in order to make sure that the sample codes are compling we place them into *.cs files.
Then we use the mdsnippets tool to render them inside the markdown files.

Please read this documentation: https://github.com/App-vNext/Polly/tree/main/src/Snippets

And here you can see a sample PR which updates some code examples inside the Polly docs: https://github.com/App-vNext/Polly/pull/2355/files

@peter-csala
Copy link
Contributor

Or as an alternative you can place the entire sample code inside the samples folder and refer that inside the docs.

@lonix1
Copy link
Author

lonix1 commented Jan 10, 2025

Sorry, I wasn't sure how to do the PR. I'm not a GitHub expert (I'm using the web interface), but I'll see what I can do.

return pipeline;

// else create pipeline with multiple strategies
var wasCreated = _resiliencePipelineRegistry.TryAddBuilder(partitionKey, (builder, context) =>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest to take a look at GetOrAddPipeline here. It would make the code simpler.

@peter-csala
Copy link
Contributor

Sorry, I wasn't sure how to do the PR. I'm not a GitHub expert (I'm using the web interface), but I'll see what I can do.

On your fork you can create a code space to use a Visual Studio Code like web-based environment for development.

codespaces

@github-actions
Copy link
Contributor

This pull request is stale because it has been open for 60 days with no activity. It will be automatically closed in 14 days if no further changes are made.

@github-actions github-actions bot added the stale Stale issues or pull requests label Mar 15, 2025
@peter-csala
Copy link
Contributor

Hey @lonix1 if you don't have time to finish this then I can take it over in the beginning of April. Do you need my help?

@martincostello martincostello removed the stale Stale issues or pull requests label Mar 15, 2025
@lonix1
Copy link
Author

lonix1 commented Mar 16, 2025

Sorry, I forgot all about this! I'm not a Github expert when it comes to PRs, so if you're willing to take the PR over the finish line I'd appreciate that, thanks. If I recall it was just a documentation change.

@peter-csala
Copy link
Contributor

My plan is that I will start working on this tomorrow.

@peter-csala
Copy link
Contributor

@lonix1 Please close this PR

@lonix1
Copy link
Author

lonix1 commented Apr 11, 2025

Thank you Peter.

@lonix1 lonix1 closed this Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants