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

Handle dotnet/extensions scenarios for HttpClient logging #87247

Closed
2 tasks
noahfalk opened this issue Jun 8, 2023 · 4 comments
Closed
2 tasks

Handle dotnet/extensions scenarios for HttpClient logging #87247

noahfalk opened this issue Jun 8, 2023 · 4 comments
Assignees
Milestone

Comments

@noahfalk
Copy link
Member

noahfalk commented Jun 8, 2023

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

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jun 8, 2023
@ghost
Copy link

ghost commented Jun 8, 2023

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

R9 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:

cc @geeknoid @dpk83 @JamesNK

Author: noahfalk
Assignees: JamesNK
Labels:

area-System.Net

Milestone: -

@noahfalk noahfalk added this to the 8.0.0 milestone Jun 8, 2023
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Jun 8, 2023
@noahfalk noahfalk changed the title Handle R9 scenarios for HttpClient logging Handle dotnet/extensions scenarios for HttpClient logging Jun 8, 2023
@ghost
Copy link

ghost commented Jun 9, 2023

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

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

Author: noahfalk
Assignees: JamesNK
Labels:

area-System.Net.Http

Milestone: 8.0.0

@CarnaViire
Copy link
Member

@noahfalk should we close this as a dupe of #77312?

@karelz karelz assigned CarnaViire and unassigned JamesNK Jul 4, 2023
@noahfalk
Copy link
Member Author

noahfalk commented Jul 4, 2023

Yeah, thats fine 👍

@noahfalk noahfalk closed this as completed Jul 4, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Aug 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants