http status code from Django REST framework
npm install @libs/status[![npm-v-badge][npm-v-badge]][npm-url] [![npm-dt-badge][npm-dt-badge]][npm-url] [![travis-ci-master-badge][travis-ci-master-badge]][travis-ci-url]
Using named status codes is more better than bare ones.
It continues using the good named style from Django REST framework
``javascript
// bad part
/**
* Although it's easy and straightforward to represent connotation
* (used status code), it's lack of denotation (concrete message)
* to represent itself.
*/
res.status(200);
// normal part
/**
* Set status code to a constant but it's not clear
* because it's only used by http.
*/
const OK = 200;
res.status(OK); // OK is 200
// good part
/**
* It's composed of status code and message as a named constant.
* It has met connotation and denotation. Therefore, it's`
* very high readable!
*/
res.status(HTTP_200_OK);
`bash`
$ npm install @libs/status
`javascript
import * as status from '@libs/status';
res.status(status.HTTP_200_OK);
`
* isInformational: (code: number) => boolean;
*
*
*
*
* HTTP_100_CONTINUE = 100;
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
[travis-ci-master-badge]: https://api.travis-ci.org/at-libs/status.svg?branch=master
[travis-ci-url]: https://travis-ci.org/at-libs/status
[npm-v-badge]: https://img.shields.io/npm/v/@libs/status.svg
[npm-dt-badge]: https://img.shields.io/npm/dt/@libs/status.svg
[npm-url]: https://www.npmjs.com/package/@libs/status