Skip to content

future plans? #1

@ferenc-radius

Description

@ferenc-radius

Any plans on improving the manager ?

In django you got things that would really help me with writing the mutations and queries
the last few weeks I have compared a lot of graphql libraries and I think this approach is great.

It would be an great start to have these in my managers by default(?):
Model.objects.getOrCreate()
Models.objects.all()
Models.objects.filter()

  • (we can come up with better names > we dont have to clone django ..)

Second in your perfect-graphql-starter project you got one 'model' query
which isn't technically a model more of a 'controller?' One class for all queries will be messy. But then I'm new to graphql so maybe I see this wrong.

Let me know, I'm happy to fork and make a proposal.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions