Upgrading the Faraday gem from version 1.0.0 to 2.0 #1
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
Updating faraday to version 2.0
…onent Replaced the URI.escape method with URI.encode_www_form_component as URI.escape method is obsolete.
…ect without a block
|
Please merge this !! |
landongrindheim
approved these changes
May 2, 2023
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.
🖼️ Context
Upgrading the
Faradaygem from version1.0.0 to 2.0.fix Azure#227
✅ Approach
faradaygem to version 2.0 from 1.0, I need to remove thefaraday_middlewareas it has been deprecated based on its docs and need to use the middlewarefaraday-follow_redirects. Details are present in the awesome-faraday docs.Faradayupgrade docs, all the adapters, except for thenet_http, have already been moved out and released as separate gems. So I had to add adapterfaraday-net_http_persistent(gem) as part of this upgrade.