Make output set of $apply transformations available for subsequent transformations or other query operators #987
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 PR fixes #945, #984
This fix makes this work:
Like you can use the output of $apply transformations,
Total
, in this case to perform subsequent transformations,$orderby
in this case.This is how the
ApplyClause
property looks like:So what happens when this is called:
if (options.Apply?.ApplyClause != null)
. ifApplyClause
is null,which will be null at this point, then theParseApply
gets called which parses the apply clause and binds the dynamic properties introduced in the$apply
transformation. This makes these properties recognizable in subsequent transformations.Before this change, the parsing of the apply clause was not happening before the
$orderby
gets called.