introducing lambda_http::IntoResponse #31
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
This lifts one more change from lando to lambda_http, the
IntoResponse
trait.This was motivated by some DX experiences I've had with
http::Response::builder()
and common cases in practice. It essentially enables handlers to return an implementation of an interface rather than a concrete type which has the ability to conversed into anhttp::Response<Body>
. This reduces ceremony and effort in constructing responses for common cases.It's also extensible for application specific types allowing your function to separate business logic from how that logic's result generates http response types
Let me know what you think.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.