My use case is that I want to effectively add an alias for a member. So here for example I add an Id property which just points to DocumentId. I need the getter of Id to be projectable for it to get translated correctly in queries, but I also happen to need a setter (it's implementing an interface). I cannot separate out the two, because if an interface defines a property as get; set; you have to implement both in one go.
[NotMapped] public string Id { [Projectable] get => DocumentId; set => DocumentId = value; }
public string DocumentId { get; set; }
For reference, the id comes from an interface like this:
interface IId<T>
{
T Id { get; set; }
}
I do need both get and set in the interface and I can't separate them out.
My use case is that I want to effectively add an alias for a member. So here for example I add an
Id
property which just points toDocumentId
. I need the getter ofId
to be projectable for it to get translated correctly in queries, but I also happen to need a setter (it's implementing an interface). I cannot separate out the two, because if an interface defines a property asget; set;
you have to implement both in one go.For reference, the id comes from an interface like this:
I do need both get and set in the interface and I can't separate them out.