diff options
| author | Michael Herold <opensource@michaeljherold.com> | 2020-10-22 21:07:14 -0500 |
|---|---|---|
| committer | Michael Herold <opensource@michaeljherold.com> | 2020-10-22 21:07:14 -0500 |
| commit | 98df995e2f0433d3d1abe46efd732bc8e20e31cc (patch) | |
| tree | 0e6471bf261fcd79dd641867ad1c50ff7b687ee8 /lib/hashie/hash.rb | |
| parent | b9a93916f538bfab57815a1d48740c826715ca5d (diff) | |
| download | hashie-98df995e2f0433d3d1abe46efd732bc8e20e31cc.tar.gz | |
Ensure all properties are set on exported Dash
When exporting a Dash via `#to_h` or `#to_hash`, we expect all
properties to be exported whether or not they are set. However, in the
change that allows codependent properties to be nilified, we regressed
the behavior of exporting all properties.
There is a gotcha here, which I note in the tests for the specs. For
posterity, MRI does not send the `#to_hash` method to anything that
subclasses `Hash` when you double-splat it. Thus, we cannot override the
behavior within MRI. For more information, see [this comment][1] where I
detail the behavior of double-splat within MRI.
Currently, JRuby also follows this behavior, but it's not guaranteed
that other Rubies will.
[1]: https://github.com/hashie/hashie/issues/353#issuecomment-363294886
Diffstat (limited to 'lib/hashie/hash.rb')
0 files changed, 0 insertions, 0 deletions