A
A
Anton2018-11-22 17:33:20
PostgreSQL
Anton, 2018-11-22 17:33:20

Is there a way to avoid boilerplate code duplication when linking C# .NET Core + Entity Framework + PostgresQL + graphQL?

I mean something like this algorithm:
1. described Entity
2. generated Entity based on them
3. based on the database (or based on Entity?) generated a graphQL scheme
(instead of manually prescribing a graphQL scheme and duplicating types)
1 and 2 does not raise questions, but the third - Googled something similar, binding to the node through some incomprehensible crutches everywhere, found one more or less understandable lib - it does not work with .net core.
Can someone clarify if it's realistic to do this, and if it's possible - with what toolset?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
Anton, 2018-11-27
@brud

he asked - he answered, here is the https://hotchocolate.io tool, in the Query object you need to register C # services, and also for the most used cases, provide https://hotchocolate.io/docs/next/dataloaders

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question