Reserved words about hashie HOT 7 CLOSED

Thanks for your bug report. I just ran into this confusing issue today.

from hashie.

I was diving into this, I think the best solution would be to have a class that inherits from Mash. Perhaps 'Smash', or 'safe mash' that raises an error when trying to assign a value to a reserved key? Thoughts?

from hashie.

I have run into this as well recently with the "display" key; Mash returns 'nil' instead of the value in the parsed data.

from hashie.

What do we want to do about this? I think this is a dup of #119, at the least. Yes?

from hashie.

I ran into the same issue with the "display" key. Although I can't actually the method in the code. I'm wondering if something else is setting this.

At the very least it should thrown an exception if you try to set a key that won't work.

from hashie.

Ran into it w/ the 'hash' key...

from hashie.

This is a duplicate of #119.

There are several ways of handling this behavior in Hashie 3.3.1:

1. If you really want to override methods with the method accessor, you can create a custom subclass that includes Hashie::Extensions::MethodAccessWithOverride. This new mixin allows you to do just that - override these methods with the keys, while retaining access to the original method(s) by aliasing them with a double-underscore prefix.
2. If you want an error when you try to set -- on a Mash -- a property that clashes with an existing method, you can mix Hashie::Extensions::Mash::SafeAssignment into your Mash class. There currently isn't an extension that just gives you a warning, but you could take a look at the SafeAssignment extension and easily write an extension that warns you instead.

I'm going to go ahead and close this issue.

from hashie.