Generic Repository Pattern shortcomings #526
linkdotnet
started this conversation in
General
Replies: 1 comment
-
|
Thank you for your diligence and attention on this topic (and project 😊). I see the issue but don't have enough knowledge to have a solid recommendation - but think a rework of this area could be worth the effort for future benefit. Would this be more of an addition on top of the current design or a rework? (I ask for breaking changes sake) Will hold off on #525 for now and happy to help where I can. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently the generic repository pattern seems to hit its limit with #525
We already have a problem inside
SimilarBlogPostas we have to "chain" calls to a repository.So we either overfetch or underfetch and have to inject more stuff to make the thing work.
The series feature showed already that for some calls we need inside the repo something like
if typeof(X) === Y then ...and that is far from ideal.So we could have a DDD style (or anything else that would allow a more "targeted" database query).
CC @digitaldirk
Beta Was this translation helpful? Give feedback.
All reactions