Make IResults types public#40704
Conversation
| public async Task ExecuteAsync(HttpContext httpContext) | ||
| { | ||
| var logger = httpContext.RequestServices.GetRequiredService<ILogger<ChallengeResult>>(); | ||
| var logger = httpContext.RequestServices.GetRequiredService<ILogger<ChallengeHttpResult>>(); |
There was a problem hiding this comment.
Do we care about changing log categories? I could see that being considered a breaking change. I don't see a huge benefit of changing it other than slightly cleaner code. @BrennanConroy @davidfowl
There was a problem hiding this comment.
I don't think this is super important for preview3, but I'd like to clarify our stance on changing log categories in general.
There was a problem hiding this comment.
Changing categories is considered a breaking change, example
There was a problem hiding this comment.
So, i think we should not change the categories. I have pushed a commit following @BrennanConroy example.
@halter73 / @BrennanConroy can you do a quick review? 00877b5
| /// <summary> | ||
| /// Gets the Content-Type header for the response. | ||
| /// </summary> | ||
| public string ContentType { get; internal set; } |
There was a problem hiding this comment.
nbd, but why internal set; instead of internal init; or just get;?
Co-authored-by: Brennan <brecon@microsoft.com>
…m/brunolins16/aspnetcore into brunolins16/iresult-apisuggestion
|
What version is this going to be released in? 8? |
|
Hi @terryaney. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |

Fix #40656