[issue-48] Ability to serialize a hash object #50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a
Hash
is passed as object, it will attempt to find attributes usingHash#[]
.PankoSerializer
must at some point turnattributes :blah
from aSymbol
to aString
, as it only works withString
keys. I think this is good enough as it'd be hard to detect which to use, and might cause confusion.I attempted to make it work with
ActiveSupport::HashWithIndifferentAccess
but was unable to get the hash lookup working in extI expect
rb_hash_lookup
is faster thanrb_funcall
with[]
but that might bypass overridden[]
method onHash
subclasses likeActiveSupport::HashWithIndifferentAccess
. Either way, it works for a plain Hash but not forActiveSupport::HashWithIndifferentAccess
and I can't figure out why (myext
experience is limited)Fixes #48