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.
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
Add a
HeaderMap
toHttpError
#1193Add a
HeaderMap
toHttpError
#1193Changes from 7 commits
69cf113
9cead09
8ff6edc
69bfd56
82d4f91
a34b66c
d69f141
5f6060a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Boxing this resolves a Clippy lint about the error type being too large. I figured we shouldn't just disable that lint, since it would presumably also trigger on user code that returns an
HttpError
, and it seems sad to have an API that results in lints in consumers if they don't go out of their way to disable them.I also considered making the field private, and requiring it be accessed via methods, since the
Option<Box<...>>
makes it a bit awkward. However, that would prevent consumers of the API from manually constructingHttpError
s by initializing the other fields, which I've seen a lot of in Omicron, so I figured it was better to just make it public.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit awkward. Another option could be to make the method take
HeaderName
andHeaderValue
only, instead of types that can be converted into them; then, it could be infallible, instead of potentially eating theHttpError
.I did it this way because it's similar to the
http::Response::builder()
API, and allows users to just pass strings as the header name/value, rather than having to convert them in user code. But, returning aResult
and maybe throwing away the error is also unfortunate. I could be convinced to change this --- what do y'all think?