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
User-defined functions can currently accept IFormatProvider and StringComparison parameters, along with the LogEventPropertyValues supplied via the expression.
The resolution logic is very basic, and only works if the "special" parameters are in the first position.
It would be great if LogEvent parameters can also be bound, and also, if NameResolver could supply additional (constant) values to bind to other arguments. Adding these things would provide a great opportunity to generalize how the expression compiler binds function parameters.
The text was updated successfully, but these errors were encountered:
User-defined functions can currently accept
IFormatProvider
andStringComparison
parameters, along with theLogEventPropertyValue
s supplied via the expression.The resolution logic is very basic, and only works if the "special" parameters are in the first position.
It would be great if
LogEvent
parameters can also be bound, and also, ifNameResolver
could supply additional (constant) values to bind to other arguments. Adding these things would provide a great opportunity to generalize how the expression compiler binds function parameters.The text was updated successfully, but these errors were encountered: