Should Microsoft.Extensions.Http.Polly be deprecated in favour of Microsoft.Extensions.Http.Resilience?
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 290
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
`Microsoft.Extensions.Http.Polly` references `Polly.Extensions.Http`, the latter of which is marked as deprecated and tells you to use `Microsoft.Extensions.Http.Resilience`, so should `Microsoft.Extensions.Http.Polly` continue to exist in a non-deprecated form? If so, when should one use `Microsoft.Extensions.Http.Polly` over `Microsoft.Extensions.Http.Resilience`?
It is also quite confusing for `Microsoft.Extensions.Http.Polly` to exist as a v8 package when it doesn't actually reference v8 of Polly.
Related: #55356
### Describe the solution you'd like
Guidance on usage of `Microsoft.Extensions.Http.Polly` going forward.
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.