[
https://issues.apache.org/jira/browse/TINKERPOP-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410279#comment-16410279
]
ASF GitHub Bot commented on TINKERPOP-1866:
-------------------------------------------
Github user spmallette commented on a diff in the pull request:
https://github.com/apache/tinkerpop/pull/823#discussion_r176567525
--- Diff:
gremlin-dotnet/test/Gremlin.Net.IntegrationTest/Gherkin/CommonSteps.cs ---
@@ -239,7 +240,8 @@ private static object ToLambda(string stringLambda,
string graphName)
private static object ToT(string enumName, string graphName)
--- End diff --
It's not really useful to this conversion, but it's the expected signature
for the lambda where this method is used. See further up in the definition of
`Parsers` where it requires a `Func<string,string,object>` a two arg function
basically. maybe we could make that nicer, but this is all plumbing code for
tests, so perhaps not a big issue?
> Support g:T for .NET
> --------------------
>
> Key: TINKERPOP-1866
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1866
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.3.1
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Critical
> Fix For: 3.3.2
>
>
> We didn't have tests for return of {{T}} which can occur with
> {{valueMap(true)}} - adding them on TINKERPOP-1860 exposed the failure in
> .NET. This may or may not be an issue for GraphSON 3.0 only. In GraphSON 2.0,
> {{g:T}} is a defined type, but it is typically not returned from the server
> outside of {{valueMap(true)}}. When that did happen in GraphSON 2.0, {{T}}
> values were simply converted to string.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
