Default rest() to ignore message templates by default
#49
+111
−67
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…; default rest() to use shallow template inspection
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is not always desirable behavior, and since it has a perf cost, it might as well be the opt-in:
Rest([deep])ExpressionTemplate, returns an object containing the first-class event properties not otherwise referenced in the template. Ifdeepistrue, also excludes properties referenced in the event's message template.LinqExpressionCompilernow uses method argument names and default values when binding function calls, so user-defined functions can have optional arguments, and we don't have to add custom rewrite rules for every function with optional args.