Skip to content
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

Document response status with empty body #1445

Conversation

madarche
Copy link
Contributor

Hello,

This is a very simple addition to the docs to explicitly document how to return a status code different than 400 when one doesn't set any body in the response.

As a new Koa user (coming from Express) this is a topic that has puzzled me at the beginning. Of course after having used Koa for a little while, the answer seems obvious. But I believe this addition will speed up even more the learning curve.

@codecov
Copy link

codecov bot commented Apr 18, 2020

Codecov Report

Merging #1445 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1445   +/-   ##
=======================================
  Coverage   99.37%   99.37%           
=======================================
  Files           4        4           
  Lines         479      479           
  Branches      128      128           
=======================================
  Hits          476      476           
  Partials        3        3           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7deedb2...e860f4e. Read the comment docs.

@dead-horse dead-horse merged commit 8ddab48 into koajs:master Apr 18, 2020
@madarche
Copy link
Contributor Author

Thanks @dead-horse. And thanks for Koa.js which is great.

@madarche madarche deleted the feat-explicitly-document-response-status-with-empty-body branch July 18, 2021 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants