-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Feature Request: ResponseBuilder
#333
Comments
Hm, perhaps adding a |
Yea, that would be perfect, actually |
I've been trying to write this, and have run up against a couple of issues. First, I planned on actually writing two The other issue is that Do you have any thoughts on this @seanmonstar? |
Yea, I noticed those too when suggesting it...
|
This adds an implementation to convert a `Response` type from the `http` crate to the `async_impl::Response` type. This is the first step to allow us to convert `http::Response` objects to `request::Response` objects This also adds an extension trait for the `http::response::Builder` type. The `http::Response` object does not provide a way to access the "final" url that the response is derived from, so we can't easily provide that in the `From<http::Response>` implementation. For users who are manually constructing `http::Response` objects for use in tests, etc, they can import this extension trait, which adds a `.url()` builder method that will allow them to pass a `Url`, which we then convert to our newtype'd Url and add to the `http::Response`'s `extensions`. Then, when converting from `http::Response` to `async_impl::Response` we can pull that value out of the `extensions` and use it to construct the `async_impl::Response` Closes #333
Related to this comment: #154 (comment)
It would be nice to be able to manually build
Response
objects so we can mock out the HTTP interactions in testsThe text was updated successfully, but these errors were encountered: