You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there some way to decouple my application when using JADNC? Lets say I have Data project where I store all my entities, and because I need to derive from Identifiable I have to add reference to it there (coupling it with ASP.Net Core)
The text was updated successfully, but these errors were encountered:
Currently, your base "Data" project would be the one to take on JsonApiDotNetCore as a dependency and then all other projects will get it as a transitive dependency. Our roadmap includes a separatuon of concerns where the current package will be split into a few packages:
JsonApiDotNetCore.Abstractions would contain all the base model definitions and would be depended upon by the other packages. So, consumers would not be required to take this on as an explicit dependency, but it would allow users like yourself to produce artifacts that depend on specific JsonApiDotNetCore types (such as Identifiable) without bringing in AspNetCore and EntityFrameworkCore.
However, at the current time this is not possible. Please let me know if this does not answer your question.
Is there some way to decouple my application when using JADNC? Lets say I have Data project where I store all my entities, and because I need to derive from
Identifiable
I have to add reference to it there (coupling it with ASP.Net Core)The text was updated successfully, but these errors were encountered: