[ https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087574#comment-16087574 ]
ASF GitHub Bot commented on TINKERPOP-1552: ------------------------------------------- Github user jorgebay commented on the issue: https://github.com/apache/tinkerpop/pull/670 I've added support for GraphSON3 on the Gremlin .NET: - Added `GraphSON3Writer` and `GraphSON3Reader`. - Modified unit tests to run using GraphSON2 and GraphSON2. I'm getting a failures on the integration tests of the .NET GLV, that start with: ``` [xUnit.net 00:00:01.2357664] Starting: Gremlin.Net.IntegrationTest [WARNING] Exception processing a script on request [RequestMessage{, requestId=bad279b8-6f42-4e47-ad08-a0343239bc1d, op='eval', processor='', args={gremlin=1, language=unknown}}]. ``` I don't understand what changed at protocol level (besides the mime type) to cause this issue. @FlorianHockmann @spmallette I will not able to dedicate time the following weeks to this. Feel free to adapt / override my changes. > C# Gremlin Language Variant > --------------------------- > > Key: TINKERPOP-1552 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1552 > Project: TinkerPop > Issue Type: Improvement > Components: language-variant > Affects Versions: 3.2.3 > Reporter: Jorge Bay > Assignee: stephen mallette > > It would be nice to have a C# GLV that runs under .NET Framework 4.5+ and > .NET Core. > The maven build could use the Exec Maven Plugin to exec .NET Core's [dotnet > test|https://www.microsoft.com/net/core#macos] command. > Some requirements, from the mailing list (edited): > {quote} > 1. The GLV should keep in line with class/method names of the java API > where possible to ensure consistency of feel across languages. > 2. There needs to be adequate tests (we're still discussing the approach to > testing GLVs and i think that needs to be tackled sooner than later as more > GLVs start to come in). Those tests should produce xunit style output > unless there is some good reason not to. > 3. There needs to be adequate documentation (e.g. Reference docs) > 4. The build/deploy process needs to be bound to maven which might be one of > the trickier bits to deal with. > {quote} -- This message was sent by Atlassian JIRA (v6.4.14#64029)