-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Handle dotnet/extensions scenarios for HttpClient logging #87247
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsR9 introduces new logging middleware for HttpClient that is different than the default logging. Ideally we want an experience that composes or upgrades, not two implementations that differ along a variety of axes. We expect the best way to get there is to be able to selectively disable the built-in logging and then adjust R9's API and behavior so that users feel like they have opted into more features (as opposed to different features). This issue tracks:
|
Tagging subscribers to this area: @dotnet/ncl Issue Detailsdotnet/extensions introduces new logging middleware for HttpClient that is different than the default logging. Ideally we want an experience that composes or upgrades, not two implementations that differ along a variety of axes. We expect the best way to get there is to be able to selectively disable the built-in logging and then adjust dotnet/extensions' API and behavior so that users feel like they have opted into more features (as opposed to different features). This issue tracks:
|
Yeah, thats fine 👍 |
dotnet/extensions introduces new logging middleware for HttpClient that is different than the default logging. Ideally we want an experience that composes or upgrades, not two implementations that differ along a variety of axes.
We expect the best way to get there is to be able to selectively disable the built-in logging and then adjust dotnet/extensions' API and behavior so that users feel like they have opted into more features (as opposed to different features). This issue tracks:
cc @geeknoid @dpk83 @JamesNK
The text was updated successfully, but these errors were encountered: