AdapterInterface causes code duplication problems.

[cyberail]

Problem begins from the, RequestHandler's reply function:
RequestHandler's reply method was returning only DioAdapter which caused chaining problems for DioInterceptor, because DioInterceptor itself needs DioInterceptor to be returned from reply to chain methods and track the History.

So we needed to distinguish returns inside the reply function, this problem was going to be solved with creating generic type parameter for RequestHandler class, but while doing this another problem occurred: reply function was not able to understand what type it was returning(DioAdapter or DioInterceptor).

For the above mentioned problem two ways of the solution were suggested to solve it.

First, define an abstract interface AdapterInterface for both, DioInterceptor and DioAdapter, also we need to define all the methods(onGet , onPost......) inside the interface and those methods will be overriden from mixin RequestRouted.
In this way reply function return type is AdapterInterface and also reply function maintains it's code completion ability when you are creating chains, But there is big problem of code management because interface defines all of the methods from ReqeustRouted with their parameters , if we have to change parameters' types or quantities of all of the methods(onGet,onPost......) inside the RequestRouted mixin we will have to change everything inside interface too.

Second, reply functions return type will be T and it will return DioAdapter or DioInterceptor with following manner: return DioAdapter() as T or return DioInterceptor() as T, In this case there is no need for separate interface but this type of solution destroyed auto completion ability for reply() method while creating chains.

For now, wile prioritizing auto completion, First method was left for use, But we are looking for other ways of solution and open to suggestions.