Comments (3)
Let's first examine what are our current limitations, and what we trying to achieve here.
This is how we use the Include for now.
public class BlogWithPostsAndAuthorSpec : BaseSpecification<Blog>
{
public BlogWithPostsAndAuthorSpec(int id) : base(b => b.Id == id)
{
AddIncludes(x => x.Include(b => b.Posts)
.ThenInclude(p => p.Author)
);
}
}
This is great, but we have the following issues:
- We can't use ThenInclude more than once. It's not chainable, so we can include 2nd level only.
- The implementation ultimately converts the expression into string. We're passing the string to EF Include methods, and not the expressions.
- From the usage perspective, the expressions are set within the AddIncludes method, which is a bit confusing.
The improved version looks as following:
public class BlogWithPostsAndAuthorSpec : BaseSpecification<Blog>
{
public BlogWithPostsAndAuthorSpec(int id) : base(b => b.Id == id)
{
// We can chain as much as we want
Query.Include(b => b.Posts)
.ThenInclude(p => p.Author)
.ThenInclude(a => a.Posts)
.ThenInclude(p => p.Author);
// We can start over with Include for another navigation
Query.Include(a => a.Posts)
.ThenInclude(p => p.Author);
// We can chain it with other methods
Query.Where(b => b.Name == "Something")
.Include(b => b.Posts)
.ThenInclude(p => p.Author);
}
}
The existing Include infrastructure won't be used, we won't need the aggregator and the Visitor pattern at all.
from specification.
The usage now is as following (we can chain several levels if we want):
public class CompanyWithStoresThenIncludeProductsSpec : Specification<Company>
{
public CompanyWithStoresThenIncludeProductsSpec(int id)
{
Query.Where(x => x.Id == id)
.Include(x => x.Stores)
.ThenInclude(x => x.Products);
}
}
Notice
The usage will be as we planned, and it has same syntax as the EF. But, I decided all those expressions to be parsed to string and stored as string, then in evaluator utilize navigationPropertyPath
of EF include. This is done based on the following reasons:
- I was doing some tests, and was surprised to find that passing string (navigation path) to EF Include, actually works faster. (probably while evaluating the expression there are a lot of checks etc).
- If we want to keep the inputs as expressions in the specifications, the actual problem is storing them. For example, we can't use
Expression<Func<object, object>>
, the delegate argument shouldn't be object. Thus, we have to storeTypes
too, and then in the evaluator we should reconstruct the whole expressions, and call the EF Include through reflection. I did this, and honestly it creates unnecessary complexity in the solution. It defies the purpose.
from specification.
This is implemented in version 4. I'm closing the issue. If anyone has additional comments or suggestions, please feel free to reply or re-open the issue.
from specification.
Related Issues (20)
- Update conventions and styling
- Update Sample projects
- Remove obsolete API
- Update pipelines.
- Including nullable/optional navigation property causes only non-nullable connected objects to be returned HOT 3
- Unable to apply Take() to a navigation property HOT 5
- Refactor and improve integration test fixtures.
- Why do the Update and Delete not returning anything? HOT 3
- Logging in the Package HOT 4
- Feature Request: Deletion of entities via specification HOT 5
- Shadow properties HOT 4
- Query to return anonymous type HOT 4
- Question: Can I some how join table "B" when my entity T does not have a navigation property to "B" ? HOT 2
- Expression Evaluation HOT 8
- Simplify Cache usage HOT 5
- DbSet<T>.WithSpecification together with ISpecification<T, TDestination> throws SelectorNotFoundException HOT 4
- Conceptual question about the ORM specific implementations HOT 2
- Is it possible to use generic repository approach like this? HOT 1
- Specification - Include with Where clause HOT 1
- Strange behavior when compare DateTime HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from specification.