-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
API Review Feedback #1506
API Review Feedback #1506
Conversation
2c02990
to
e316681
Compare
At this point I'm finding #1233 too unwieldly to follow so I've stopped keeping up to date with it. How many more changes are we expecting before we actually freeze the public API unless there's specific user feedback in an issue? |
Codecov Report
@@ Coverage Diff @@
## main #1506 +/- ##
==========================================
- Coverage 83.91% 83.86% -0.06%
==========================================
Files 273 272 -1
Lines 6503 6481 -22
Branches 1026 1020 -6
==========================================
- Hits 5457 5435 -22
Misses 837 837
Partials 209 209
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Hopefully not too many. We are trying to wrap the API by the end of the month. It's mostly about hiding/dropping some stuff and polishing the surface. Just thinking, would opening a new PR with something like |
Possibly. The main problem I have is that the diff is massive so looking for inline comments when I've marked a file as reviewed is difficult, and there's so many comments on the PR that most of them are hidden if they're old: |
Let me give a shot at this tomorrow. There are maybe 10 comments left to address. Some of these came just recently, however it might be good to have something where one is not immediately lost :) |
Details on the issue fix or feature implementation
ResilienceContext.ResilienceEvents
ResiliencePipeline.Null
toResiliencePipeline.Empty
Outcome<>
propertiesRateLimiterRejected.RetryAfter
Contributes to #1233
Confirm the following