Gremlin Native JavaScript Stringification

Do you think that there’s any value in creating a JavaScript Native API for Gremlin? Under the hood this would do a stringification of the fluent commands to generate the code to execute. So the quick start would look something like this:

import { createGraph } from 'gremlin';

const g = createGraph();

g.V().has('name', 'Alice').execute((err, results) => {
  if (err) {
    return console.error(err)
  }

  console.log(results);
});

// Or with "sugar" any method that accepted a variable number of pairs of
// parameters could also accept an object a la:
const q = {name: 'Alice'};
g.V().has(q).execute((err, results) => {
...

WDYT?

[davidcrouch]

I’ve pretty much implemented what guyellis is asking for and can also confirm the pain mentioned by PommeVerte. I developed it as part of a higher-level ORM implementation and only implemented the steps that I needed, which was about 30% of all TP3 steps.

It works and is a hack, but maintenance will be a pain and I don’t think it is a smart strategy for the long term due to different TP release support not to mention the limitations with regard to supporting the Groovy language in general (not an issue for me though).

Just my $0.02.

[jbmusso]

I closed this issue as it’s outside of the scope of the driver, though I’m open to continue this conversation here.