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.

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

MMRecordAttributeAlternateNameKey is ignored if the value can be found using the default key #114

Open
sstigler opened this issue May 19, 2015 · 0 comments
Milestone

Comments

@sstigler
Copy link

For example:

{id: 123,
name: "outer",
inner:
{ id: 456,
name: "inner" }
}

Although MMRecord only provides default access to the outer dictionary, I would really like both the name and ID of the object represented by the inner dictionary. While MMRecordAttributeAlternateNameKey will work as expected for inner.name, if I specify inner.id I will get a value of 123 instead of 456.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants