graphql or rest?

[Hame-daani]

questions

• [x] authentication?
  • needs third party -_-
  • not realy that hard (https://www.youtube.com/watch?v=pyV2_F9wlk8)
• [x] serializers?
  • does have modelform
• [x] views?
  • theres only one path and view
• [x] admin panel?
• [x] how does modelform works? does it need to be customized?
• [x] permissions?
  • use graphene-permissions or graphene-cud

[Hame-daani]

compare to REST

https://www.reddit.com/r/django/comments/q9jsqi/django_rest_framework_stop_nesting_serializers/

pros

• only one endpoint
• easier for related models

cons

• hard auth (needs third party)
• probably needs custom mutations

[Hame-daani]

example

https://www.youtube.com/watch?v=ZWZFhRPjNYU rest qraphql

• graphiql (debugger) (its builtin. you can add it in urls.py)

[Hame-daani]

extension of main graphene

https://graphene-django-cud.readthedocs.io/en/latest/index.html

pros

• builtin mutations
• support nested fields
• support permissions
• field validation

another

https://github.com/0soft/graphene-django-plus

[Hame-daani]

mutations

using graphene-django-cud

• on user
  • add, update, delete user
  • add, delete friendrequest
• on review
  • add, update, delete comment
  • add, delete like
• on comment
  • add, update, delete comment
  • add, delete like

[Hame-daani]

permissions

using django-graphene-permissions

one permission as IsOwner

• on node for view
• on mutation only owner or superuser

[Hame-daani]

graphql toturial

https://www.howtographql.com/