Fixed Issue: Objects and arrays get wrong parent if they have text nodes as siblings

[NitinRamnani]

Link to issue: #320

Fix: brothers Id was being passed to addEdgeToGraph() in traverse() which was adding incorrect edge, that is, it was adding edge from brother to the node. Fixed it by passing brother's parentId so that new edge is created between parent and node.

Input:

{
  "body": [
    {
      "text": "klsadfkjasf",
      "jo": "mo",
      "object": {
        "test": 2
      },
      "array": [
        {
          "text": "khjasd",
          "operation": "lksfj",
          "action": {
            "url": "test.com"
          }
        }
      ]
    }
  ]
}

Output before:

Output After:

[TallTed]

@NitinRamnani — Your initial comment will be much easier to understand, if you edit it to add two lines that contains only three backticks, as below —

```

One such "code fence" goes below the line reading Input:, and the other goes above the line reading Output before:.

[AykutSarac]

We'd consider adding it to settings and not enabling by default because it serves a different mode of view. Current one is making it easier to understand, but your implementation makes it more correct.

[AykutSarac]

Taking feedbacks for which one's readability is better:

{
  "image": "golang:latest",
  "stages": [
    "test",
    "build",
    "deploy"
  ],
  "format": {
    "stage": "test",
    "script": [
      "go fmt $(go list ./... | grep -v /vendor/)",
      "go vet $(go list ./... | grep -v /vendor/)",
      "go test -race $(go list ./... | grep -v /vendor/)"
    ]
  },
  "compile": {
    "stage": "build",
    "script": [
      "mkdir -p mybinaries",
      "go build -o mybinaries ./..."
    ],
    "artifacts": {
      "paths": [
        "mybinaries"
      ]
    }
  },
  "deploy": {
    "stage": "deploy",
    "script": "echo \"Define your deployment script!\"",
    "environment": "production"
  }
}

[mahtikebab]

Thanks for fixing this!

@AykutSarac Definitely the fixed version (1) is better because it's correct. I don't understand how (2) would be better because it's clearly describing a faulty relationship between the nodes compared to the JSON. If we want to have a hierarchy like the one in image 2 we need to describe it in the JSON structure also, i.e. the "image": "golang:latest" is a parent of the other nodes