By EF conventions, in a many-to-many relation, you have two standalone entities and a third entity between them which represents a relationship bridge.
Fiyaz Hasan
A collection of 34 posts
My Notebook: Redux & NGRX
Application state is subjected to change. A reducer is a pure function that takes the current state and an action been dispatched upon it. Depending on the action type it produces a new state and returns it. States are immutable.
GraphQL with .NET Core (Part - VIII: 1-Many Entity Relations)
You can configure entity relationship following entity framework conventions. Entity framework will auto-create a one-to-many relationship between entities if one of the entity contains a collection property of the second entity. This property is known as a navigation property.
GraphQL with .NET Core (Part - VII: Data Persistence)
This post focuses more on configuring a persistent data storage rather than discussing different aspects of GraphQL. With that being said, let's connect to an in-memory database for fake testing.
GraphQL with .NET Core (Part - VI: Queries & Mutations)
We've come to the point, where you should have a good understanding of GraphQL Queries already. Few things you should keep in mind though, A query should never change the value of a field. In other words, it should always fetch and never modify. Queries are executed in parallel.
GraphQL with .NET Core (Part - V: Fields, Arguments, Variables)
At its simplest, GraphQL is about asking for specific fields on objects. Let's extend our simple application to accommodate a complex type.
GraphQL with .NET Core (Part - IV: GraphiQL IDE)
GraphiQL (pronounced graphical) is an in-browser IDE for exploring GraphQL. I think it's a must-have tool for any server running behind GraphQL. With GraphiQL in place, you can easily give yourself or your team an in-depth insight into your API.
GraphQL with .NET Core (Part - III: Dependency Injection)
ASP.Net Core has a built-in dependency injection container. It's simple and can serve our purpose very well. Not only it can be configured to serve implementations to abstractions but it also can control the lifetime of the created instances.