Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use nested hashes instead of string keys #17357

Merged
merged 1 commit into from
May 18, 2018
Merged

Use nested hashes instead of string keys #17357

merged 1 commit into from
May 18, 2018

Commits on Apr 27, 2018

  1. Use nested hashes instead of string keys 

    This avoids needing to generate a new string value for each key on
setting of the value and retrieving, and the extra hashes are not a huge
consumer of space.

Of note, the keys are now not strings at all.  Top level will be the
class names, and the child keys will be just the raw IDs.  The
@ems_xml_nodes value is not used anywhere besides the lookup that was
changed in this commit, so the change of this structure should not have
an adverse affect... hopefully...
    @NickLaMuro
    NickLaMuro committed Apr 27, 2018
    Configuration menu
    Copy the full SHA
    ef73d6e View commit details
    Browse the repository at this point in the history