-
Notifications
You must be signed in to change notification settings - Fork 768
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
Adds enhanced support for proxy models. #603
Adds enhanced support for proxy models. #603
Conversation
abettke
commented
Mar 27, 2019
- Allows for proxy models to be used directly in DjangoObjectType definitions.
- Updates tests for proxy model support.
- Removes test showing proxied DjangoObjectType definitions fail.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need any documentation to go along with it?
None that I can think of. This just adds, what seems to me, expected behavior. Beforehand, using a proxy model in a DjangoObjectType threw a GraphQLError. Now, it fully supports using proxy models the same way that base models are used. |
…jango into fix/enhanced-proxy-model-support
I'm waiting with bated breath for this :) |
For anyone needing this immediately (as my company did), my fork contains theses changes, and as far as I know is currently up to date with master. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great work!
Note to anyone searching: Upgrading from 2.2.0 to 2.4.0 resolved my issue with serializing a taggit proxy model. Thanks all who worked on this! |