Closed HParker closed 8 years ago
I responded to the comments and squished the commits.
I think this is ready to merge. Yes, it would be nice to unify the code between Hash
and Vector
, but I think that can be done in a separate PR. @dubek, would you like to merge?
Does it make sense to add dig to the Associable module we already have? On Dec 7, 2015 00:56, "Alex Dowad" notifications@github.com wrote:
I think this is ready to merge. Yes, it would be nice to unify the code between Hash and Vector, but I think that can be done in a separate PR. @dubek https://github.com/dubek, would you like to merge?
— Reply to this email directly or view it on GitHub https://github.com/hamstergem/hamster/pull/216#issuecomment-162418117.
Does it make sense to add dig to the Associable module
It does. dig
is about recursive retrieval from nested, associable structures.
Merged manually ( 500928ea887793960977a000ae9a937197e1cbc1 ).
@HParker thanks a lot for your contribution to Hamster (and the explanations about Ruby 2.3 shenanigans)! If you'd like to continue working on it, I suggest (in a new PR):
Vector#dig
#dig
in the Associable
module and removing it from Hamster::Hash
.
Part of #212
Hamster::Hash#dig matching ruby 2.3.0
I am not experienced with the branching convention or documentation style, so I would appreciate advice there.