[TINKERPOP-2714] Ensure that Gremlin translation matches its original form

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.5.2
• Component/s: process, translator
• Assignee: Unassigned
• Reporter: Stephen Mallette
• Created: 01/Mar/22 11:34
• Updated: 01/Mar/22 11:34

Description

It's not clear if there are other places where this is an issue but with the introduction of property(Map) we've made it so that this call unwinds to property(k1,v1).property(k2,v2)... which isn't exactly what the user typed. So when you hit translation, it might be confusing to see the latter representation. Not sure if this is a major problem at this time and it seems the value of the new overload from property() outweighs this concern, but in the longer run we should probably look to ensure the two things remain equivalent.