design-patterns-explained-with-food VS Specification

Design Patterns Explained with Food

I was wondering why you are not using abstract methods but instead declaring the method as virtual and throwing NotImplementedException, like [here](https://github.com/wesdoyle/design-patterns-explained-with-food/blob/main/StructuralPatterns/Bridge/FarmersMarketVendor.cs)?

If so, then look into this

Also, to minimize duplication of code and optimize your architecture i suggest using something like https://github.com/ardalis/Specification

This is a great candidate project for the Ardalis.Specifications library.

This is honestly such an amazing way to make sure you have a clear view of what your Linq does, see https://github.com/ardalis/Specification - note that the examples on the front git page uses a repository, but he later allowed the use directly on DbSet which finally made it possible for me to use the library.

Check out the specification pattern - it is designed to encapsulate query logic similar to your example. Steve Smith has a nice library for it on GitHub: https://github.com/ardalis/Specification

I'm thinking that the only way to abstract both of them would be to have the repositories return IEnumerables and have well defined aggregates for the entire application to avoid an exploding number of methods on the interface, but this is not possible in my project*. I've looked at Steve Smith's Specification library, but since it works with IQueryable, it would not work with Dapper.