IMHO:

1. ErrorDecoder is called by ResponseHandler that is used by *MethodHandler. Users usually do not call it manually. We do not call it in any Client's child.
2. There is the (default) decode method that have two parameters that it ignores. For me it is bad way.
3. Why do we need to pass maxBodyBytesLength and maxBodyCharsLength each time when we call the decode method? I guess these values are the same.

If the question "How to set maxBodyBytesLength and maxBodyCharsLength" the solution is "use the constructor": we can add another constructor that gives these parameters and passes them to errorStatus(String methodKey, Response response, Integer maxBodyBytesLength, Integer maxBodyCharsLength).

As far as I see you have implemented it :)

IMHO:

1. ErrorDecoder is called by ResponseHandler that is used by *MethodHandler. Users usually do not call it manually. We do not call it in any Client's child. 2. There is the (default) decode method that have two parameters that it ignores. For me it is bad way. 3. Why do we need to pass maxBodyBytesLength and maxBodyCharsLength each time when we call the decode method? I guess these values are the same.

If the question "How to set maxBodyBytesLength and maxBodyCharsLength" the solution is "use the constructor": we can add another constructor that gives these parameters and passes them to errorStatus(String methodKey, Response response, Integer maxBodyBytesLength, Integer maxBodyCharsLength).

As far as I see you have implemented it :)

Yeah I realized later that via constructor it is much simpler and does not require breaking change