Job Guldemeester

Did you configure the the [logging](https://pub.dev/packages/logging)? When I tried using the `HttpLoggingInterceptor` I had to include the logging package and include it in order to see any messages. ``` Logger.root.level...

Woeps other default line length configured :) But reformatted the files now

> Also, since you're already doing this it might make sense to also update the generator to use the `Request.uri` constructor instead of the default one that still uses `String`s....

Did a bunch of refactors to use `Uri` throughout the code base. But it's mostly replacing the `String`s with `Uri` at the moment. Probably I have to rethink some stuff...

From the comments I think its partly solved. When I refactored bits of the logging interceptor I faced the same problems. A possible solution could be to refactor the whole...

I doesn't solve the cause of the exception. But I added a test see #600 to verify that exception are passed up in the interceptor chain. This doesn't mean that...

I understand the Interceptor are not throwing the exception but I don't understand what is expected when a exception is thrown by the Converter. I don't think it matter where...

Thanks for elaborating more on the issue. I don't think there's much we can do. One way I can think of is providing a way to insert a "logging" interceptor...

Yes that indeed why interceptors exist, only with the requirement that the request can be converted and the flow doesn't throw errors. The other idea behind chopper is that it...

I think the `BodyType` and `InnerType` are correct. This is usually used in for `List` and `Map` objects to determine the types. But in this case that `InnerType` would be...