[ 
https://issues.apache.org/jira/browse/TINKERPOP-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette updated TINKERPOP-2378:
----------------------------------------
    Issue Type: Improvement  (was: Bug)

There was a fair bit of discussion about this issue when Gremlin.NET was first 
written. Ultimately the choice was made to use naming semantics similar to what 
.NET programmers would expect, thus upper case method names. Generally speaking 
the thinking is that Gremlin should look more like the programming language it 
is hosted in rather than "Gremlin written in Groovy". Personally, I'm not in 
favor of departing from this approach and in fact have long wanted to make 
gremlinpython more pythonic in nature and less "groovy". 

Of course, I do understand the pain there. Debugging a traversal in Gremlin 
Console to then manually do the conversion to another language is annoying. 

What did you mean by:

> Could we have `outE` and `OutE` projections for C#? 

Do you just mean overload functions like "OutE" with "OutE"? If so, I'm not 
sure I'd be in favor of that.

[~jorgebg] [~florianhockmann] any ideas on how to ease the pain of using a REPL 
like Gremlin Console which is Groovy based and then having to convert from that 
dialect to a particular programming language that doesn't look like Groovy? I'm 
not sure there is going to be a good general approach to this though...how 
would one do this for Clojure or Go language variants. 

Is the answer here to just use the REPL of the language you are coding in? If 
i'm doing Ogre, I use the Clojure REPL to debug my traversal. I think I do the 
same with Python. Thoughts?



> Make C# DSL to be more closer to standard (lower case extensions) 
> ------------------------------------------------------------------
>
>                 Key: TINKERPOP-2378
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2378
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: dotnet
>    Affects Versions: 3.4.6
>            Reporter: Dzmitry.Lahoda
>            Priority: Minor
>              Labels: c#, dot_net, dsl, generator
>             Fix For: 3.5.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Usually, I prototype queries via gremlin console or azure cosmos console. I 
> use first small letter in traversal steps. For example, 'outE`. Porting to 
> strongly typed DSL requires to update all lower case steps into upper. Like, 
> 'OutE`. It is very tedious process. Could we have `outE` and `OutE` 
> projections for C#? It would make my life much more pleasant and C# closer to 
> Gremlin standard. All such cases of differences do apply. C# has extensions 
> and static using and case sensitive and dynamic. So most stuff in place to 
> make C# to Groovy almost one to one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to