-
Notifications
You must be signed in to change notification settings - Fork 203
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
Replace rash with rash_alt #136
Conversation
Do faraday_middleware support ruby <= 1.9.2 ? It seem my branch fail in only ruby <= 1.9.2... |
@mislav can you check this? We'd like to go ahead with rash_alt in debian. |
I've marked this for next release (0.12) as the plan is to remove support for ruby < 1.9.3 |
@shishi can you please pull/rebase from master? |
I've waited for long time 😄 It's time to be done finally! I'm very glad. |
Really sorry about the wait @shishi! |
See following links for more details: https://github.com/lostisland/faraday_middleware/releases/tag/v0.12.0 lostisland/faraday_middleware#136
* Pin faraday_middleware to version 0.12.0 * Replaces rash dependency with rash_alt See following links for more details: https://github.com/lostisland/faraday_middleware/releases/tag/v0.12.0 lostisland/faraday_middleware#136 * amend version lock for faraday_middleware
Since Hashie have own Rash, rash gem have problem of conflict namespace. We discussed this from long time ago.
tcocca/rash#9
But there is not any solution, I released rash_alt gem for solving out-of-dependency.
faraday_middleware use both hashie and rash, there is problem for out-of-dependency. This pull request solve this problem.