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

Already on GitHub? Sign in to your account

Tastypie compatibility #186

Merged
merged 2 commits into from Jun 11, 2013

Conversation

Projects
None yet
2 participants
Contributor

lutoma commented Jun 11, 2013

This patch makes neo4django compatible with the tastypie API framework by adding the get_internal_type function and some variables to the model and relationship base classes.

Owner

mhluongo commented Jun 11, 2013

Ha, the get_internal_type() implementation is kind of a hack, but I guess not more than the rest of properties.py :) Does this cover nested resources, or are you still looking into that?

Owner

mhluongo commented Jun 11, 2013

Regardless, this looks good. Thanks!

@mhluongo mhluongo added a commit that referenced this pull request Jun 11, 2013

@mhluongo mhluongo Merge pull request #186 from lutoma/patch-tastypie-compat
Tastypie compatibility
333a88c

@mhluongo mhluongo merged commit 333a88c into scholrly:master Jun 11, 2013

1 check passed

default The Travis CI build passed
Details

@lutoma lutoma deleted the lutoma:patch-tastypie-compat branch Jun 11, 2013

Owner

mhluongo commented Jun 15, 2013

I just ran into a question on StackOverflow about this (http://stackoverflow.com/questions/16920180/create-rest-api-with-neo4j-and-django/17127413#17127413) and tried to explain how to get neo4django and tastypie working with these patches. I was able to get resources working, but not nested resources- did you ever figure that out? Would love to share this / include it in the docs.

Contributor

lutoma commented Jun 15, 2013

Hm, yes. You have to manually specify those in the ModelRessource class. I don't know why that doesn't happen automatically :(

Owner

mhluongo commented Jun 16, 2013

Gotcha, thanks!

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