tcocca / rash Goto Github PK

rash gem have out-of-dependency problems since Hashie had own Rash, I released rash-alt gem. This is just resolving rash's problems, I didn't change excpept that problems.

rash_alt accepted faraday_middleware, instead of original rash gem, to resolve out-of-dependency. If someone is in trouble as same situation, you can use rash_alt instead of original rash.

#9
https://rubygems.org/gems/rash_alt
lostisland/faraday_middleware#136

Currently, rash specifies a dependency on hashie ~> 1.2.0. I tried updating this dependency to allow version 2.0 but this resulted in a test failure: https://gist.github.com/317cde6786318bcb5041

Could you please look into why this is happening and release a new version of rash that is compatible with the latest version of hashie?

Thanks!

Thanks for building rash! I've used jt in the past to build API clients.

I've been helping out with hashie recently and pushed out hashie 2.0. Would you be interested in adding rash to the hashie gem?

We're using a gem that requires rash but to use it, we have to downgrade our hashie gem from 2.1.2
to 2.0.5, would it be possible to upgrade that dependency?

Hashie now have own Hashie::Rash.
https://github.com/intridea/hashie/blob/master/lib/hashie/rash.rb

So, I think rash have to rename other name. Or, we can not use rash with future version Hashie...
But Faraday Middleware use Rash, and there is already rash user.

It seem hashie rename their own rash is better?