EntityFrameworkCore.Projectables icon indicating copy to clipboard operation
EntityFrameworkCore.Projectables copied to clipboard

Project over properties and functions in your linq queries

Results 38 EntityFrameworkCore.Projectables issues
Sort by recently updated
recently updated
newest added

If I try to define 2+ projectable methods with the same name on the same class but give them different argument lists, then the source generator triggers an error indicating...

enhancement
help wanted

I'm working on a large project with more than 1000 entities. When I add a reference to EntityFrameworkCore.Projectables nuget package, it drastically deteriorates Visual Studio - Peek definition and Go...

enhancement

This request contains a solution to problem https://github.com/koenbeuk/EntityFrameworkCore.Projectables/issues/71 and a test case of use. The request was prepared with the support of P9avel.

My Entity `QualityDataPart` implements an interface `IQualityDataPart` which has a property `Type` (string). In order to save storage this text is stored in a different Entity `QualityDataPartInfo ` Now I...

enhancement
help wanted

Is it possible to have a fluent option instead of using attributes? It would be nice if I could set this in the entity configuration on the `EntityTypeBuilder` `builder.Projectable(...)`

enhancement
help wanted

I am having a problem where this library is working perfectly in development with `dotnet dev`, but when I run the app generated with `dotnet publish -c Release`, none of...

In my project I user EFCore.BulkExtensions for batch update or Delete I upgraded my nuget package these two days ,After upgrading and testing one package after another,Eventually I found out...

help wanted

With Projectable attr, I can select the property direct via Select and/or use as judgement. But directly query the set will not include projectable property. Env: .net6/EFcore7 ``` using System.ComponentModel.DataAnnotations;...

enhancement

On #90 and #92, I added navigation queries on the last `.Select` call to keep included properties on the returned entities, but doing so actually made EF fetch all relations...

This allows projectable properties to be marked as `OnlyOnInclude` and only opt-in root query rewriting by explicitly calling a `.Include(x => x.ProjectedProperty)`. This was discussed in #84 by @yinzara. PS:...