Provide Response Code Enums

What kind of issue is this?

• Feature Request. Start by telling us what problem you’re trying to solve. Often a solution already exists! Don’t send pull requests to implement new features without first getting our support. Sometimes we leave features out on purpose to keep the project small.

I believe this library will benefit from having the Response object return an Enum on its method code(), like many other HTTP libraries and Frameworks do., so instead of:

if (response.code() == 200) { 
    // print "OK".
} else if (response.code() == 403) {
    // print "Forbbiden"
}

In which we have to memorize all the HTTP codes, and maybe mix some, we can have:

if (response.code() == HttpStatus.OK_200) { 
    // print "OK".
} else if (response.code() == HttpStatus.Forbidden_403) {
    // print "Forbbiden"
}

I think this will help the users to code quicker with the library (autocomplete can help with Enums) and beginners on REST and HTTP codes will be less prone to errors and mixing up what code does what.

[swankjesse]

If ya want constants there are some here: https://docs.oracle.com/javase/8/docs/api/java/net/HttpURLConnection.html

[feinstein]

I think the code becomes more readable, maybe you guys deal with HTTP codes for a long time and don’t see the difference, but for beginners all those numbers on the middle of the logic can get a bit hard to read smoothly.

Just my $0.2