Error logs filled with "You are setting a key that conflicts with a built-in method Hashie::Mash#count ..." #13
Description
It looks like at some point the Hashie library started wanting to use the .count attribute that the API also returns. This ends up flooding the logs with the message below as things get loaded in:
You are setting a key that conflicts with a built-in method Hashie::Mash#count defined in Enumerable. This can cause unexpected behavior when accessing the key as a property. You can still access the key via the #[] method.
You are setting a key that conflicts with a built-in method Hashie::Mash#count defined in Enumerable. This can cause unexpected behavior when accessing the key as a property. You can still access the key via the #[] method.
You are setting a key that conflicts with a built-in method Hashie::Mash#count defined in Enumerable. This can cause unexpected behavior when accessing the key as a property. You can still access the key via the #[] method.
[repeats 185 more times]
A cursory look around the internet turned up this issue in a few other repositories (including the Hashie library itself):
- Wrapping results in Hashie::Mash 3.5.1 causes logs to be flooded with warnings elastic/elasticsearch-ruby#398
- Warnings when parsing hash: WARN -- : You are setting a key that conflicts with a built-in method Hashie::Mash#size defined in Hash. This can cause unexpected behavior when acces sing the key via as a property. You can still access the key via the #[] method. hashie/hashie#423
- You are setting a key that conflicts with a built-in method Hashie::Mash#object_id goshippo/shippo-ruby-client#49
The path forward appears to be either to disable the warning, or wrapping the result sets in a subclass instead.