Ruby - rubocop Method too long

[DanRathbun]

@eneroth3

Heavily use of hashes is a typical sign that object orientation isn’t fully utilized. Often the content of such a hash can be properties of the object. In my experience the code gets less cluttered and more easily readable when you can access these values directly by name instead of having to specify both the hash and the key.

@Nick_G

A hash can be memory intensive, and you might consider creating a factory pattern to produce what you need, that would be easier to maintain in the future.

A meta-programming coding exercise (from Aug 2018) in creating a data class factory …

• OpenStruct vs Struct vs custom data classes

Avoids the pitfalls of Struct, and as easy to use as OpenStruct (and avoids it’s quirks as it doesn’t use an internal Hash nor override the class object’s method_missing callback.)