[TINKERPOP-2432] Generate correct toString() representation of bytecode in Javascript

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.4.8
• Fix Version/s: 3.5.0, 3.4.9
• Component/s: javascript
• Assignee: Stephen Mallette
• Reporter: Serg Salo
• Created: 02/Oct/20 22:48
• Updated: 14/Oct/20 12:27
• Resolved: 14/Oct/20 12:27

Description

I have a very simple task - generate bytecode using typescript traversal. 

for example: 
const g = new Graph().traversal();
const q = g.V().hasLabel("airport").where(__.outE("route").hasId(7753));
const query = new translator("g" as any);
const bytecode = q.getBytecode();
console.log(`Bytecode: ${bytecode.toString()}`);
 
Here is what is generated: 
 
Bytecode: [["V"],["hasLabel","airport"],["where",{"graph":null,"traversalStrategies":null,"bytecode":

{"sourceInstructions":[],"stepInstructions":[["outE","route"],["hasId",7753]]}

,"traversers":null,"sideEffects":null,"_traversalStrategiesPromise":null,"_traversersIteratorIndex":0}]]
 
Looks like it does the first level serialization correct, but the second level isn't properly serialized. 
 
any suggestions what is wrong with this code?

Issue Links

• is related to: TINKERPOP-2403 Gremlin javascript Translator does not handle child traversals