Greetings @davidfowl !
Awhile back I needed help with something, and you helped answer my issue.
The way your library handles parsing for the HttpResponse object - is it superior to the suggested answer there?
In my case, I first parse the object to a json string (using JsonSerializer.Deserialize), and then I pass it to the HttpResponse object by its WriteAsync method, which utilizes the new System.IO.Pipelines API, followed by a HttpResponse.Body.FlushAsync call.
Looking forward to hearing from you!
Greetings @davidfowl !
Awhile back I needed help with something, and you helped answer my issue.
The way your library handles parsing for the HttpResponse object - is it superior to the suggested answer there?
In my case, I first parse the object to a json string (using
JsonSerializer.Deserialize), and then I pass it to the HttpResponse object by itsWriteAsyncmethod, which utilizes the newSystem.IO.PipelinesAPI, followed by aHttpResponse.Body.FlushAsynccall.Looking forward to hearing from you!