Koen
Thanks @ZvonimirMatic and @PhenX for staying on top of this! I'll publish a new preview build soon.
I like this, though I'm somewhat in doubt if this is really desired. By default in EF you'll get all properties when you select an Entity. If you want to...
> I wonder if there's a way that we can tell EF to skip those properties. I would say we want to select these but based on the projectable expression....
We would essentially want to translate: `dbContext.Entity` into `dbContext.Entity.Select(x => new Entity { Id = x.Id, Alias = x.Alias })` This is not a trivial undertaking. If you want to...
#84 Is another example of an expression that could be closed if we were to rewrite QueryRootExpressions
@zoriya No, this would only make it so that all projectable members of the source type will be expanded. A user can still apply additional Select expressions which will essentially...
Thanks for suggesting this, I agree that this should be supported and the suggested approach sounds fair.
Having a projectable property on the concrete entity type as you have in QualityDataPart is supported. Your sample code is therefore supported and when I run this: ```csharp using System;...
This seems to be an issue that will hard to solve. `Expression test = p => p.Type == "Test";` doesn't inform this library what concrete type `IQualityDataPart` actually is and...
@JodliDev This will not work. In your example, The implementation of `GetData` is still a blackbox for EF and since the method is not marked as a `Projectable`, there are...