Make using custom headers easier/nicer #94
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.
With this commit you can go from having to write:
to writing:
It's a small change, but given we already have something similar for sending a
body
with a customcode
—very handy for when a custom response code is needed—to me it only makes sense we have one for custom headers, something that gets set far more often.Sorry if this may be out of scope, I just found it a personal annoyance having to write
Http200,
every time just because I needed a custom header.Lastly, I do not know wether or not this should have the
{. inline .}
pragma or not.