HotChocolate integration with dapper

Product

Hot Chocolate

Is your feature request related to a problem?

N/A

The solution you'd like

I have done a generic and dynamic integration between Dapper and Hot Chocolate using the IResolverContext. This implementation will be very useful to the community, and it only requires a plain object type.

GitHub https://github.com/CristianBarragan/Coffee-Beanery

Supports:

• Nodes (Left joins between entities)
• Edges (Joins between entities)
• Manages mutations for any generic objects
• Paging
• Filtering
• Sorting

It is on my to-do list to make it public. I believe this repo would be the best place for this code. It is in an infant state, and there are optimizations and new features to do, as well as testing.

The idea is to test the code against the API itself, similar to the EF strategy https://learn.microsoft.com/en-us/ef/core/testing/choosing-a-testing-strategy#overall-comparison.

Start by reviewing the linked Coffee-Beanery repository and its generic Dapper integration using IResolverContext. Compare the proposed API-level testing approach with the linked EF testing strategy. Done would mean a reviewed integration in the Hot Chocolate project with coverage for joins, mutations, paging, filtering, sorting, and testing.