Skip to content

Conversation

kmcgrath
Copy link
Contributor

If the request is for an add or remove blueprint then populate needs to be used instead of find. This is so the parentid and id are parsed correctly.

Without this change the id from the relation is used by find to look up the parent model.

@kmcgrath
Copy link
Contributor Author

The rabbit hole got a bit deep here. Would really like to get blueprints with associations working. I think this could be a good start, but I'm willing to pull this back as it is hitting more and more code.

This also might be a duplicate of issue #5

@kmcgrath kmcgrath changed the title Feature/find target objects populate Support populate blueprints Jul 31, 2015
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

Successfully merging this pull request may close these issues.

1 participant