You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have to type response codes manually such as 200, 403, e.t.c as part of response closure. Though it is not that hard to remember most commonly used response codes, its not easy to remember the meaning of each response code.
It would be much more helpful for developers if there is a provision for uses to use methods like ok() which can refer to HTTP status code 200
This can function similar to existing API of HttpHeaders which allows users to write accept() instead of typing 'Accept'
This makes the API less error prone & more readable
The text was updated successfully, but these errors were encountered:
thekalinga
changed the title
Add support for HTTP response codes
Add support for built in HTTP response codes
Mar 13, 2018
thekalinga
changed the title
Add support for built in HTTP response codes
Add support for built in HTTP status response codes
Mar 13, 2018
Type: Enhancement
Currently we have to type response codes manually such as 200, 403, e.t.c as part of response closure. Though it is not that hard to remember most commonly used response codes, its not easy to remember the meaning of each response code.
It would be much more helpful for developers if there is a provision for uses to use methods like
ok()
which can refer to HTTP status code200
This can function similar to existing API of
HttpHeaders
which allows users to writeaccept()
instead of typing'Accept'
This makes the API less error prone & more readable
The text was updated successfully, but these errors were encountered: