You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/04/07 20:58:00 UTC

[jira] [Commented] (TINKERPOP-3047) Grammar does not parse keywords into Map keys

    [ https://issues.apache.org/jira/browse/TINKERPOP-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941713#comment-17941713 ] 

ASF GitHub Bot commented on TINKERPOP-3047:
-------------------------------------------

spmallette opened a new pull request, #3091:
URL: https://github.com/apache/tinkerpop/pull/3091

   https://issues.apache.org/jira/browse/TINKERPOP-3047
   
   Major refactoring to the grammar itself, translators. Removed a few gherkin tests that tested lambdas which weren't really necessary given they will be reserved for embedded cases. Changed infinity/nan to be able to parse to float.
   
   VOTE +1




> 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)