-
Notifications
You must be signed in to change notification settings - Fork 44
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
Latest version incompatible with faraday 1.0.0 #73
Comments
Thanks for bringing this up. Try fixing it? |
@dblock It doesn't seem like Faraday can be upgraded in development. I tried to clone and force faraday to be version 1.0.0, but the gem danger-changelog is not compatible. And that gem has not been updated since faraday 1.0.0. I'm not confident enough to try to figure out a solution to that one, if it was just a question of changing the word "use" with the word "adapter" I can do that, but this seems a bit more complicated. |
thanks @nielsjansendk i can try look at this. Thanks for reporting 💜 |
I've tried to just change word "use" with the word "adapter" and it works, but not in every case :( |
I see the fix for this was merged to master, any chance a version could be released with this fix? |
sure, good reminder! I can release a new version in a bit. |
Awesome, thank you! |
Just released the new version |
Using graphlient 3.7 with Faraday 1.0.0 results in the following error:
RuntimeError (Adapter should be set using the
adaptermethod, not
use)
It is likely this problem: https://stackoverflow.com/questions/58162859/upgrading-faraday-gem-runtimeerror-adapter-should-be-set-using-the-adapter-m that happens with faraday versions higher than 0.15.4
As far as I can tell from the source code of graphlient, the faraday adapter is set using the "use" method (here: https://github.com/ashkan18/graphlient/blob/0b36f9fc30fc290de98e67d9313b5f3d2681288f/lib/graphlient/adapters/http/faraday_adapter.rb). If my undestanding of the problem is correct, this will need to change to be compatible with Faraday 1.0.0 .
The text was updated successfully, but these errors were encountered: