Coercion problems with Hashie::Mash about hashie

[wapcaplet]

I discovered that I can work around part of this limitation by coercing both the string and symbol, i.e.:

coerce_key :user, 'user', User  

This allows tweet.user, tweet[:user], and tweet['user'] to all be coerced properly, but Tweet.new(:user => ...) still doesn't do coercion.

[wapcaplet]

I managed to make these use cases work with relatively few changes to Mash and Coercion. Please consider merging this pull request, and let me know if any further changes are needed to maintain backward compatibility.

[jch]

Thanks for the pull. It's been a busy week, but I'll try to take a look
this weekend ;)

On Thursday, May 9, 2013, Eric Pierce wrote:

I managed to make these use cases work with relatively few changes to Mash
and Coercion. Please consider merging this pull requesthttps://github.com//pull/96,
and let me know if any further changes are needed to maintain backward
compatibility.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/95#issuecomment-17680271
.

-Jerry
@whatcodecraves http://twitter.com/whatcodecraves
github http://github.com/jch