Summary

Resolve #901 - Add user-facing HTTP status code constants

Add HTTP status code constants to allow more readable status code comparisons, usage instead of hard-coded integres.

Changes

Implemented constants

2xx: OK, CREATED, ACCEPTED, NO_CONTENT
3xx: MOVED_PERMANENTLY, FOUND, NOT_MODIFIED, TEMPORARY_REDIRECT, PERMANENT_REDIRECT
4xx: BAD_REQUEST, UNAUTHORIZED, PAYMENT_REQUIRED, FORBIDDEN, NOT_FOUND, METHOD_NOT_ALLOWED, CONFLICT
5xx: INTERNAL_SERVER_ERROR, BAD_GATEWAY, SERVICE_UNAVAILABLE

Example

In http.ez, Added some use HTTP status code use cases

...
if resp.status != http.OK {
        println("Request Failed: ${resp.status}")
        return
}
...
if post_resp.status != http.CREATED {
        println("Request Failed: ${post_err.message}")
        return
}
...

Test Results

Manual tests

Unit tests

Integration tests

Formatting