Skip to content
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

Make ReactiveResilienceStrategy public #1460

Merged
merged 3 commits into from
Aug 8, 2023

Conversation

martintmk
Copy link
Contributor

@martintmk martintmk commented Aug 8, 2023

Details on the issue fix or feature implementation

It is used as a base class for all reactive strategies. It should be public.

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

@martintmk martintmk added the v8 Issues related to the new version 8 of the Polly library. label Aug 8, 2023
@martintmk martintmk added this to the v8.0.0 milestone Aug 8, 2023
/// <param name="context">The context associated with the callback.</param>
/// <param name="state">The state associated with the callback.</param>
/// <returns>
/// An instance of pending <see cref="ValueTask"/> for asynchronous executions or completed <see cref="ValueTask"/> task for synchronous executions.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
/// An instance of pending <see cref="ValueTask"/> for asynchronous executions or completed <see cref="ValueTask"/> task for synchronous executions.
/// An instance of a pending <see cref="ValueTask"/> for asynchronous executions or a completed <see cref="ValueTask"/> task for synchronous executions.

/// <remarks>
/// <strong>This method is called for both synchronous and asynchronous execution flows.</strong>
/// <para>
/// You can use <see cref="ResilienceContext.IsSynchronous"/> to determine whether the <paramref name="callback"/> is synchronous or asynchronous one.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
/// You can use <see cref="ResilienceContext.IsSynchronous"/> to determine whether the <paramref name="callback"/> is synchronous or asynchronous one.
/// You can use <see cref="ResilienceContext.IsSynchronous"/> to determine whether <paramref name="callback"/> is synchronous or asynchronous.

@martintmk martintmk enabled auto-merge (squash) August 8, 2023 05:41
@codecov
Copy link

codecov bot commented Aug 8, 2023

Codecov Report

Merging #1460 (21725b1) into main (975369a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1460   +/-   ##
=======================================
  Coverage   83.92%   83.92%           
=======================================
  Files         274      274           
  Lines        6506     6506           
  Branches     1012     1012           
=======================================
  Hits         5460     5460           
  Misses        837      837           
  Partials      209      209           
Flag Coverage Δ
linux 83.92% <ø> (?)
macos 83.92% <ø> (ø)
windows 83.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed Coverage Δ
src/Polly.Core/ReactiveResilienceStrategy.cs 100.00% <ø> (ø)
src/Polly.Core/ResilienceStrategy.cs 100.00% <ø> (ø)
...Utils/CompositeResilienceStrategy.DebuggerProxy.cs 100.00% <ø> (ø)

@martintmk martintmk mentioned this pull request Aug 8, 2023
4 tasks
@martintmk martintmk merged commit b1ec863 into main Aug 8, 2023
@martintmk martintmk deleted the mtomka/make-ReactiveResilienceStrategy-public branch August 8, 2023 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v8 Issues related to the new version 8 of the Polly library.
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants