Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make service layer independent of persistence framework
See original GitHub issueI am currently writing an IEntityRepository implementation for MongoDB, for which there is no EF support.
The code for Filter and Sort is the same and PageAsync only differs in its query realization in that instead of ToListAsync() it is ToAsyncEnumerable().ToList().
To avoid code duplication for those methods I suggest adding an abstract class that handles Filter, Sort and PageAsync for all DB drivers that can provide an IQueryable<>, with an abstract method for DB-specific query realization.
That abstract class would only depend on IJsonApiContext.
Alternatively the query realization could be in its own interface for DI.
What do you think?
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
My employer gave me permission. I will try to upload my (not great) code today. How can I reach you?
awesome! you can DM me on the project’s Gitter site