Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/915
> Is there a good reason for not exposing the StatusCode on the
ResponseException as well? I'm not familiar enough with the protocol to say
whether that's an internal detail or something the consumer should be able to
react to.
No, there is no good reason for not exposing it. I also thought about
exposing it but didn't get around yet to actually implement it. It makes sense
to expose the `StatusCode` in my opinion as it helps users to implement a
better error handling. The Java driver also [already exposes
it](https://github.com/apache/tinkerpop/blob/7a814e196519775079005cdf9bc73ec934302891/gremlin-driver/src/main/java/org/apache/tinkerpop/gremlin/driver/exception/ResponseException.java#L46).
I think that it would also fit well with the other changes in this PR. So,
if you want to address that as well, then I'd say go ahead and do so.
---
