-
Notifications
You must be signed in to change notification settings - Fork 438
Update faraday adapter to support Faraday 2.0 #686
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
Comments
@i0rek what do you think about a separate gem/project? |
If the recommendation is to create a separate gem, I am up for it. |
I created https://github.com/typhoeus/faraday-typhoeus. |
Thanks @Kjarrigan @i0rek, great to see things moving! Also feel free to close this issue if you want to, now that you've decided on how to proceed 👍 |
Hi @Kjarrigan @i0rek, just a quick nudge to let you know that Faraday 2.0 has shipped. |
typhoeus support for faraday 2 not ready yet typhoeus/typhoeus#686
@iMacTia I've got a decent pass here: |
Hello there,
I'm Matt from the faraday core team, and I bring some exciting news 🎉 !
We're closing in on releasing Faraday 2.0 and with this release, we've made big changes on the way we manage adapters.
The biggest of these is that now adapters are not bundled anymore, and are instead shipped into their own, separate gems!
No more dependencies mess, no more 1st class and 2nd class adapters, power to the community 💪
What does this mean for Typhoeus?
Although these will be little, some changes to the current Typhoeus adapter will be required in order to support Faraday 2.0. You're free to keep it inside this repository, if you like, but our suggestion would be to move it into a separate one. We've created a handy template repo to make that process really easy, and we're available if you need any help!
You can see an example of this with the faraday-net_http adapter.
We'd love to keep Typhoeus in the faraday family, even after v2.0 is finally released, so please feel free to reach out if you need any help or guidance with this!
The text was updated successfully, but these errors were encountered: