[
https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029505#comment-16029505
]
Jesse Carter commented on TINKERPOP-1552:
-----------------------------------------
Hey guys, been watching this issue with a lot of interest as we're currently
invested heavily in Gremlin in a .NET shop and would love to see more native
language support.
Just wanted to weigh in on my thoughts regarding Naming Convention. According
to the official Tinkerpop docs for gremlin language variants
http://tinkerpop.apache.org/docs/3.2.1-SNAPSHOT/tutorials/gremlin-language-variants/
the intention is that the language variant should follow the language
conventions of the host language:
"Every programming language is different and a Gremlin language variant must
ride the fine line between leveraging the conventions of the host language and
ensuring consistency with Gremlin-Java. A collection of conventions for
navigating this dual-language bridge are provided.
If camelCase is not an accepted method naming convention in the host language,
then the host language’s convention should be used instead. For instance, in a
Gremlin-Ruby implementation, outE("created") should be out_e("created")."
Besides what seems to be the recommendation from the TinkerPop team, I think
that PascalCase would be more approachable for .NET devs, not to mention that
some productivity tools such as Resharper or CodeCop like to flag these sorts
of things as style warnings for not matching C# convention.
> 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.3.15#6346)
