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

CircuitBreaker should be always host specific #44

Closed
Ceridan opened this issue Oct 30, 2020 · 1 comment
Closed

CircuitBreaker should be always host specific #44

Ceridan opened this issue Oct 30, 2020 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@Ceridan
Copy link
Contributor

Ceridan commented Oct 30, 2020

Remove separate logic for host specific and generic CB. We should leave only host specific CB.

@Ceridan Ceridan added this to the v2.0.0 milestone Oct 30, 2020
@Ceridan Ceridan added the enhancement New feature or request label Oct 30, 2020
@Ceridan
Copy link
Contributor Author

Ceridan commented Nov 2, 2020

Will be released in version v2.0.0.

See milestone v2.0.0

@Ceridan Ceridan closed this as completed Nov 2, 2020
@Ceridan Ceridan mentioned this issue Dec 5, 2020
Ceridan added a commit that referenced this issue Dec 5, 2020
Milestone v2.0.0

Milestone include major changes including breaking changes.
Full list of changes:
- Fix namespace clash between Dodo.HttpClient and System.Net.Http.HttpClient (#32)
- Add OverallTimeoutPolicy (#13)
- AddDefaultPolicies is renamed to AddResiliencePolicies (#45)
- CircuitBreaker is host specific by default. Host agnostic version is removed (#44)
- HttpClientSettings is replaced with ResiliencePoliciesSettings (#38)
- Add support of Retry-After http header (#40)
- Refactor API for end-users (#51)
- Re-write README (#24)
- Add .NET 5 support (#53)
- Fix flaky test (#52)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant