-
Notifications
You must be signed in to change notification settings - Fork 349
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
ODataException for key-parens segment following OperationSegment with parameters #2754
Labels
Comments
ODL has this test case to dis-allow key in parenthesis after composable function with parameters as: [Fact]
public void KeyLookupCannotAppearAfterFunctionWithParameters()
{
PathFunctionalTestsUtil.RunParseErrorPath("People(1)/Fully.Qualified.Namespace.AllMyFriendsDogs(inOffice=true)(1)", ODataErrorStrings.ExpressionLexer_SyntaxError(14, "inOffice=true)(1"));
} However, We do think it should be valid to have key in parenthesis after composable function with parameters. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use of ODataUriParser for a Uri containing a key-segment following a composable function returning a collection of entities:
Assemblies affected
All up to 7.18.0.
Reproduce steps
Expected result
A valid ODataPath is returned when the key-parens syntax is used (identical to the one returned when the key-as-segment syntax is used).
Actual result
An ODataException is thrown.
The text was updated successfully, but these errors were encountered: