-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Re-implement the FormReader on top of the PipeReader #3967
Copy link
Copy link
Closed
Labels
DoneThis issue has been fixedThis issue has been fixedarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsfeature-pipelinesAnything relating to exposing/using Pipes in ASP.NET CoreAnything relating to exposing/using Pipes in ASP.NET Core
Milestone
Metadata
Metadata
Assignees
Labels
DoneThis issue has been fixedThis issue has been fixedarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsfeature-pipelinesAnything relating to exposing/using Pipes in ASP.NET CoreAnything relating to exposing/using Pipes in ASP.NET Core
Type
Fields
Give feedbackNo fields configured for issues without a type.
To verify that our pipe adapter actually works, we should change FormReader to use PipeReader and verify that the pipe adapter works. Eventually, we will optimize FormReader to not use an adapted pipe and obtain the PipeReader directly from a feature, but this will give us confidence that the PipeAdapter is usable.