future plans?

[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.

[zvictor]

Hi @ferenc-radius! Thank you for showing interest in our project.

The design of the managers API will be very important for this project to thrive. The managers, however, are very dependant on a good API coming from the connectors/adapters and that's the reason why I will focus first on building those. After we have a more clear idea on how we will standardise the data coming to the managers, it will be easier to build the manager API on top of it.

Nevertheless, it would be exciting to see a fork and proposals coming from your side. It could lead to a different and better way to design the managers. 😃

About your second point, I am not sure I understand your question. Are you talking about /domain/models/Query.js?