New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow using Faraday 1.x release in gemspec #421
Conversation
Require < 2.x, but greater than 0.9
The EtagCache middleware caches the response `env` structure to allow restoring a cached response, but the `body` attribute is no longer real data, it dynamically dispatches to either `request_body` or `response_body`. This causes an `env` being cached with a `response_body` value but no `body` value on cache hit/read, triggering a nil body to downstream middleware.
@nogates Apologies for the noise on this. Found/fixed two backward compatibility issues, but this should be good to go and ready for review. You seemed like the most active maintainer, but please let me know if I should ask someone else to review. |
I tested these changes with |
Friendly ping on this, I'd love to get a review. |
Thanks for the PR @wpeterson and sorry for the delay in merging this! |
Thanks for working on this @wpeterson! @nogates would it be possible to get a new release cut soon? This is the last blocker on us updating our faraday version at Discourse. Let us know if there's anything we can do to help. |
I am so sorry it has taken me such a long time to release the latest version. I had just pushed it to rubygems. |
@nogates @davidtaylorhq Thanks to you both for your help getting this work in! |
Faraday has released a 1.0 version last month, but
zendesk_api
depends on the0.x
series of Faraday versions by gemspec.Let's allow using the latest version of Faraday but avoid a major upgrade to
2.x
by maintaining a version constraint.Backward compatibility fixes (v. 0.9 - v 1.x compatible):
Faraday::Error
module which was removed in v0.9.0
of Faraday.