-
Notifications
You must be signed in to change notification settings - Fork 766
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
[WIP] Improve form and serializer mutations #546
Conversation
1 similar comment
@patrick91 any plans to update this pull request? |
@firaskafri I'd love to, but I don't have much time right now, I might try to work on it during DjangoCon Europe sprints :) |
@CharlesBradshaw can you update @patrick91 todo list? |
66c3875
to
ea2cd98
Compare
0e6fa16
to
fd516a3
Compare
My current attempt at supporting Global IDs as part of form mutation lookup does a hard type check:
For an |
I think adding a "resolve_instance" class method to |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This PR improves both FormMutation and SerializerMutation to add support for better error types and wrapping the return type for the SerializerMutation.
I've also removed the ModelFormMutation since I think it is easier to use one class, and I'm not sure why it was possible to customize the model class there too.
TODO:
Feel free to add comments and notes even if this is still a WIP.
[1] My idea is to add support for customizable errors via a setting property
NOTE: this is going to have some breaking changes (errors and return types have changed)