refactor: Switch from reqwest to ureq
#296
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This switches our http client library that we use to fetch images from
reqwesttoureq. There are some API differences between the two libraries, so things can't be handled quite the same way (primarilyureqdoesn't have something akin to aClient), and there are differences in how http responses are handled, but that shouldn't have any practical impact on us unless servers are returning valid images with http error codesThis drops all the
tokiorelated stuff from our (non-dev) dependency tree (20 less dependencies, and release lto builds are over a MiB smaller)