Community Note
- Please use a 馃憤 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
- If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Describe the bug
This issue occurs running a %%gremlin query that returns path components in elementMap format. If the vertices in the path contain a custom id property, the visualizer confuses this with the default T.id token property, and renders the graph incorrectly.
When using WebSockets protocol, this issue manifests as duplicate, unconnected nodes in the graph.

Community Note
Describe the bug
This issue occurs running a
%%gremlinquery that returns path components inelementMapformat. If the vertices in the path contain a customidproperty, the visualizer confuses this with the defaultT.idtoken property, and renders the graph incorrectly.When using WebSockets protocol, this issue manifests as duplicate, unconnected nodes in the graph.