[
https://issues.apache.org/jira/browse/TINKERPOP-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941980#comment-17941980
]
ASF GitHub Bot commented on TINKERPOP-3047:
-------------------------------------------
spmallette commented on code in PR #3091:
URL: https://github.com/apache/tinkerpop/pull/3091#discussion_r2033832236
##########
gremlin-test/src/main/resources/org/apache/tinkerpop/gremlin/test/features/map/Order.feature:
##########
@@ -34,24 +34,6 @@ Feature: Step - order()
| ripple |
| vadas |
- Scenario: g_V_name_order_byXa1_b1X_byXb2_a2X
Review Comment:
removed for lambdas. given
https://issues.apache.org/jira/browse/TINKERPOP-3136 it was more trouble to
figure out the problem than to just get a head start on that issue. these tests
already exist in embedded.
> Grammar does not parse keywords into Map keys
> ---------------------------------------------
>
> Key: TINKERPOP-3047
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3047
> Project: TinkerPop
> Issue Type: Bug
> Components: language
> Affects Versions: 3.7.1
> Reporter: Stephen Mallette
> Priority: Critical
>
> {{[keys: ["a","b"]}} won't work because "keys" ends up being parsed to
> {{Column.keys}}. another issue at play is the use of parens to wrap certain
> key definitions but not others. it doesn't feel consistent. like, it will
> work for {{T}} values but not for something like "edges" which is just a
> keyword token. Not sure it's wrong but it requires some examination.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
