Standardise the error return from http request about genqlient HOT 3 OPEN

That seems like a sensible thing to add, but I'm not sure offhand what the API would look like. We could add an As-able error type I guess? What do you mean by "the standard error"? Does net/http, or some other stdlib package, have a thing we should be using?

BTW, you can already (a) get direct access to the error and/or (b) retry it by writing your own graphql.Client, or passing a modified http.Client which, say, retries on 429. But I can see how sometimes you would want to know the status code in the application code instead.

from genqlient.

I mean, we can standardise the error messages and return those error messages when something is happening.

On my situation, at the moment i am using strings.prefix to match if there is a 429 error. While implementing the standard error messages, I can just compare the returned error with the gql client provided error. It's a nicer way to handle errors isn't it?

from genqlient.

Yeah, looking more there really doesn't seem to be a standard. Ah well, I guess we can make our own As-able error. We already document As-ability to gqlerror.List (and should probably mention it on client.MakeRequest as well) so we can add similar mention there.

Anyway, PRs are welcome! I think this should be a pretty easy one.

from genqlient.