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
This article implies that if I have 10 entities which have the same field "IsDeleted" I need to copy-paste the filter 10 times.
Basic OOP expects to have a single base entity with the field and the rule applied on the base level.
At the moment I greatly struggle with EF Core trying to do exactly this and nowhere can find applicable article.
In my case a large number of 3rd pty tables having StatusId field, which I mage though basic abstract class HasStatus.
The best so far is that I manage to enumarate though all entities but can't apply a filter, as there is no generic to accept the base type. HasQueryFilter accepts LambdaExpression, which is a bummer.
@DimitryNechaev This is one of the usability issues around query filters that are being tracked on dotnet/efcore#21459. Closing this as a duplicate of that issue, with a reference to here.
This article implies that if I have 10 entities which have the same field "IsDeleted" I need to copy-paste the filter 10 times.
Basic OOP expects to have a single base entity with the field and the rule applied on the base level.
At the moment I greatly struggle with EF Core trying to do exactly this and nowhere can find applicable article.
In my case a large number of 3rd pty tables having StatusId field, which I mage though basic abstract class HasStatus.
The best so far is that I manage to enumarate though all entities but can't apply a filter, as there is no generic to accept the base type. HasQueryFilter accepts LambdaExpression, which is a bummer.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: