EF Core Code Generation MVP

[benmccallum]

Adds EF Core code generation and an analyzer so that we can go SDL-first --> EF model --> DB.

Functionality:

• Analyzer
• Code generation project
• EF entities generation (from object types that will be backed by a table)
• EF DbContext generation (with DbSet members for object types that will be backed by a table)
• @schemaConventions directive (with pluralized table names option) (addresses cloud#116)
• @table directive (with name property to specify custom table name mapping) (addresses cloud#117)
• PK determination (@key, falling back to Id-looking field, falling back to auto-created field using schema convention) (addresses cloud#112)
• A bunch of other stubbed directives that don't do anything yet
• GQL Query type generation
• Field resolver per table entity (with IQueryable, x attr, y attr, z attr)
• Startup DI code generation

Concepts:

• As a schema object type is processed, a context is built up that allows us to capture things like PK, table name, etc and build up our knowledge of the SDL as we need to generate code. This will help us in the future when we start doing more complicated directives for things like relations.

Testing:

• Snapshooter test coverage of the raw code generated
• Integration testing (as per Neo4J, that also compiles the source) (likely another PR)

[benmccallum]

@michaelstaib , this is ready for review really. Tomorrow I'm gonna:

• add a couple of tests for the PK stuff and
• add the code generation for the DI part, which I'll try copy the solution from the Neo4J one for

But you should start reviewing it in any case if you have the time.

[michaelstaib]

I think we do not need this once I have merged my generator improvements.

[benmccallum]

Have those improvements made it in? Looks like Neo4J equivalent is doing the same thing still but let me know if I need to adjust anything, though perhaps better as a new branch.

[michaelstaib]

Once I reworked directives we could also have a constructor that passes this in.

[michaelstaib]

It is nice that you collocate the type wit the model.

[benmccallum]

Yea I know it was against the original code but it made it a lot easier to copy-paste and easier to build out. They're fairly light on, so I think it's ok.

[michaelstaib]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
23 Code Smells

0.0% Coverage
1.5% Duplication

[benmccallum]

@michaelstaib , would this be a problem?

I have a scenario where I'd like to be able to loop the directives of a field, finding those that implement an interface, but then actually get the directive class, but .ToObject<T> doesn't cut it as T in my case would be an interface and the Activator code fails. Have a look at how it's used in SchemaExtensions::GetDirectivesWhereRuntimeTypeImplements

[benmccallum]

Usage:
directive.ToObject<IXyzDirective>(directive.Type.RuntimeType)

[stale]

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.