-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Why doesn't the ViewComponentResultExecutor use the IHttpResponseStreamWriterFactory #4885
Labels
Milestone
Comments
Likely an oversight. @rynowak was profiling view execution code paths - aspnet/Mvc#3248, might have missed view components. |
@mkArtakMSFT 2.2? Can't I just send a PR for this now? |
@davidfowl, do it please! |
I’ll do it |
@davidfowl 2.2, or 3.0? |
3.0 at this point. |
aspnet-hello
added
1 - Ready
area-mvc
Includes: MVC, Actions and Controllers, Localization, CORS, most templates
bug
This issue describes a behavior which is not expected - a bug.
labels
Dec 14, 2018
pranavkm
added a commit
that referenced
this issue
Apr 16, 2019
ghost
locked as resolved and limited conversation to collaborators
Dec 4, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to replace the HttpResponseStreamWriter with a (potentially) more efficient version and it turns out the ViewCompomentResultExector doesn't use it https://github.com/aspnet/Mvc/blob/133dd964abb1c2a4167cf38faa38fe0319b7b931/src/Microsoft.AspNetCore.Mvc.ViewFeatures/ViewFeatures/ViewComponentResultExecutor.cs#L108. Is that intentional or just an oversight?
/cc @rynowak @pranavkm
The text was updated successfully, but these errors were encountered: