Michael Herold

What I'm looking for here is a simplification of our integration test setup. The implementation is a suggestion: if there's a different way you want to go about attempting it,...

### Analysis I looked into this some. The main issue with the example is that `Hashie::Mash` deep_updates the source hash when passing into the initializer. So this: ``` ruby TweetMash.new(:user...

Bump @maxlinc - Just wanted to check if you've worked on the changes you mentioned back in January. I like the idea of a persistable framework and between the work...

Building on what dB said earlier, I think this should be able to be easily done using [coercion procs](https://github.com/intridea/hashie#coercion-proc). If it's not, show us an example and we can look...

What types of things would you want to validate? Type "validations" can be done using the [property translation mixin](https://github.com/intridea/hashie/blob/master/lib/hashie/extensions/dash/property_translation.rb#L28) (i.e. the behavior that Trash adds to Dash).

Things I want to add for doc testing: 1. Integrate it into the default Rake task so it runs on Travis. The current Rake task in the library doesn't work...

That would be a great long-term plan. I think the way the dry-rb project does it is interesting.

Because there is already an `Enumerable#grep`, I wonder if this would be better as `DeepGrep`? Since that's what it's adding.

Hi @vmarutha, thank you for your contribution! I've started to dive into this and I have a few things that I've found. 1. Could you please add an implementation of...

Hi @vmarutha, Sorry, it looks like you might have been waiting for feedback, which was my mistake. I'll answer your questions from your last message. > So I tried that...