Minor fixes for importing related entities #600

Closed
wants to merge 2 commits into
from

Conversation

Projects
None yet
2 participants
@KentMcCullough

No description provided.

@tonyarnold

This comment has been minimized.

Show comment Hide comment
@tonyarnold

tonyarnold Jan 1, 2014

Contributor

Hi Kent — do you have a specific example where this was failing? I'd like to put together a test for what this fixes.

Contributor

tonyarnold commented Jan 1, 2014

Hi Kent — do you have a specific example where this was failing? I'd like to put together a test for what this fixes.

@ghost ghost assigned tonyarnold Jan 1, 2014

@KentMcCullough

This comment has been minimized.

Show comment Hide comment
@KentMcCullough

KentMcCullough Jan 9, 2014

The first commit fixes importing a child entity as a parent entity. e.g. User entity has Instructor and Student sub entities, it will allow you to import either when the relationship is to the User entity.

The second uses the mappedKeyName value of the userInfo dictionary when importing a relationship as opposed to a specific property.

The first commit fixes importing a child entity as a parent entity. e.g. User entity has Instructor and Student sub entities, it will allow you to import either when the relationship is to the User entity.

The second uses the mappedKeyName value of the userInfo dictionary when importing a relationship as opposed to a specific property.

@tonyarnold

This comment has been minimized.

Show comment Hide comment
@tonyarnold

tonyarnold Apr 8, 2014

Contributor

These appear to have been fixed in 7e4c076 and 13cbe84. Thanks!

Contributor

tonyarnold commented Apr 8, 2014

These appear to have been fixed in 7e4c076 and 13cbe84. Thanks!

@tonyarnold tonyarnold closed this Apr 8, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment