Move tesla adapter to config

[prtngn]

Delete tesla adapter config from client.ex for the opportunity to config from config files.

[visciang]

Hi @prtngn! The idea of making the HTTP library pluggable leveraging the Tesla abstraction is not bad. It gives the possibility to stick to the same HTTP library you decided to use, not only at app level but also down to your deps (as much as they all are open to this kind of configurability).

But there are some considerations we should pay attention to:

• If the HTTP adapter library is pluggable (choosing among the tesla availble adapters) then the responsibility of it will be on the client. For example the client should explicitly install on its side the deps (ie for the gun adapter: gun, castore, idna ...) along side with the telegram dep. It should also correctly configure the adapter opts (timeouts, certs_verification etc).
• Should telegram library give you out of the box a default one, that you can eventually override?
• About the "adapter configuration" aspect we should think if it's OK to use the global config approach from the app vs lib perspective (in general it's not)

I think you understand it needs a bit of investigation before jumping to a conclusion. I'll think about it. Feel free to discuss here if you want.

Thank you

[prtngn]

Thanks for you answer. And big thanks for this library.

So, you right ) I only learning elixir ) I faced a problem with self-signed certificate+proxy and that's why I need to config Tesla adapter. I think it is a good idea to stay default Tesla config in telegram module and give opportunity to config Tesla adapter in program config.

But I don't understand how I can do it ))