-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make aliases created in compute() transformation visible for following transforms/query options #1369
Make aliases created in compute() transformation visible for following transforms/query options #1369
Conversation
token.Kind.ShouldBeEquivalentTo(QueryTokenKind.Compute); | ||
List<ComputeExpressionToken> tokens = token.Expressions.ToList(); | ||
tokens.Count.Should().Be(3); | ||
tokens[0].Kind.ShouldBeEquivalentTo(QueryTokenKind.ComputeExpression); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it's more clear to create a private method to verify # 1, # 2, # 3 separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have test ParseComputeWithMathematicalOperations that checks $compute for that case. I'm adding the same for compute()
...lTests/Microsoft.OData.Core.Tests/ScenarioTests/UriParser/FilterAndOrderByFunctionalTests.cs
Outdated
Show resolved
Hide resolved
...lTests/Microsoft.OData.Core.Tests/ScenarioTests/UriParser/FilterAndOrderByFunctionalTests.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…g transforms/query options (OData#1369) * Ensure that we can use aliases genearted in compute on later stages * Ensure that we can use aliases genearted in compute on later stages * Extra tests for compute * Code alignment
…g transforms/query options (#1369) * Ensure that we can use aliases genearted in compute on later stages * Ensure that we can use aliases genearted in compute on later stages * Extra tests for compute * Code alignment
Issues
*This pull request fixes issue #1368 * also adds a few tests for ApplyBinder (it wasn't covered in original implementation)
Description
Collecting aliases generated in compute() transformation to make them visible for following transformations and/or query options ($orderby, $filter)
Checklist (Uncheck if it is not completed)