BeagleNetworkInterceptor is misleadingly named about beagle

[pandulapeter]

Thanks for raising the issue I'll look into it!

[pandulapeter]

Sorry to hear about that, I hope you didn't spend too much time debugging before figuring out it wasn't your fault. I can change the name of the class in the next update and improve the documentation to avoid confusions.

Just to be clear: did using addInterceptor() instead of addNetworkInterceptor() fix your issue? If not, do you have any suggestions of what I should change to not mess up the compression?

[angusholder]

No worries, I didn't mean it to come across as pointing blame!

Yeah addInterceptor fixed it. I suppose this is more of an OkHttp problem, it can be easy to mix up which kind of interceptor you have, and it will mostly work when you do it wrong, just ends up being hard to debug 💀

I think BeagleNetworkInterceptor could be adjusted to take the Content-Encoding: gzip header into account, but I don't know if it would be worthwhile, there might be other ways in which it doesn't work properly when inserted as a network interceptor, probably better just to document clearly which kind of interceptor it is.

Thanks for the quick reply!

[pandulapeter]

In v2 the interceptor is accessed using Beagle.interceptor and the KDoc for the relevant class also contains a code snippet., so hopefully there will be no more confusion.