ayrat555
refactor(client-ureq): remove mime_guess
While tinkering on #260 I noticed that mime_guess doesn't seem to be required. Everything I tested worked fine without. But I only tested with quite small files and the officially hosted bot API servers, not a self-hosted one.
reqwest also depends on mime_guess, so I'm not sure whether its used internally for the client-reqwest multipart stuff there. It's also possible to specify a mime with reqwest multipart, but it's not done there. Either it's not required at all or reqwest does the assumption internally which doesn't seem the case to be currently, but I haven't looked far.
@ayrat555 @pxp9 do you have any thoughts on this? There should probably more testing before something like this is changed.
Could you simulate big tests or something like that?
Just to be sure it is not breaking code.
Thank you in advance @EdJoPaTo
for me it's ok. not sure if telegram uses provided mime type. maybe we can try uploading a couple of files and check how they are displayed in telegram
as self-hosted bot API servers seem to have different handling of files in more places, I think its a good idea to do these tests against them too.
I think I'll just leave it as is and drop this PR. #260 simplifies this mime_guess logic and it's not a big dependency.