Hi,
first of all: I really like Zifts approach and the code is very nice.
My problem is that it currently lacks custom mappings to be able to filter and sort complex or dynamic types. In my case I have some entities that store a JsonDocument for dynamic properties. It would be cool if one could define custom mappings to access these as nested properties, maybe via a lambda. Gridify has this for example.
Currently BuildPathSegmentExpression throws when generating the expression property, as it assumes a "normal" object. Here it would be cool if I could attach somehow and specify that I want to use a JSON property instead.
Maybe it's a bit difficult to explain this and I get that this might not be a common case.
Hi,
first of all: I really like Zifts approach and the code is very nice.
My problem is that it currently lacks custom mappings to be able to filter and sort complex or dynamic types. In my case I have some entities that store a JsonDocument for dynamic properties. It would be cool if one could define custom mappings to access these as nested properties, maybe via a lambda. Gridify has this for example.
Currently BuildPathSegmentExpression throws when generating the expression property, as it assumes a "normal" object. Here it would be cool if I could attach somehow and specify that I want to use a JSON property instead.
Maybe it's a bit difficult to explain this and I get that this might not be a common case.