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
I'm currently writing a custom LINQ Parser as documented here.
The example IsBlue uses the MemberFor method to obtain a locator for the property:
var locator = memberCollection.MemberFor(expression).TypedLocator;
However, MemberFor is a member of LinqInternalExtensions that is marked internal (as indicated by its name). It took me a while to figure out why this doesn´t work locally :-)
Would it make sense to make a number of the internal extensions method public? They are tremendously useful for writing custom LINQ parsers. In particular, I'm using MemberFor() to find the correct JsonPathSegment and ReduceToConstant() to obtain the arguments of the MethodCallExpression.
(For now, I've copied both methods to my own repo).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm currently writing a custom LINQ Parser as documented here.
The example
IsBlue
uses theMemberFor
method to obtain a locator for the property:However,
MemberFor
is a member ofLinqInternalExtensions
that is markedinternal
(as indicated by its name). It took me a while to figure out why this doesn´t work locally :-)Would it make sense to make a number of the internal extensions method public? They are tremendously useful for writing custom LINQ parsers. In particular, I'm using
MemberFor()
to find the correctJsonPathSegment
andReduceToConstant()
to obtain the arguments of the MethodCallExpression.(For now, I've copied both methods to my own repo).
Beta Was this translation helpful? Give feedback.
All reactions