Connect to children multiple parents

[andrico1234]

Connect to children multiple parents

[andrico1234]

I would love something like this.

With the current data structure, which looks like so:

[
  {
    name: 'Parent One',
    children: [
      {
        name: 'Child One',
        children: []
      }
    ]
  },
  {
    name: 'Parent Two',
    children: []
  }
]

'Child One' will never be able to referenced by 'Parent Two', or any other parent for that matter.

Without thinking about the problem space for too long, two potential solutions come to mind:

The first would be to flatten the structure, so that instead of a nested tree structure, like above, each parent would have a collection of foreign keys that reference the primary key of a child:

[{
  [
    id: 'parentOne',
    name: 'Parent One',
    children: ['childOne', 'childTwo']
  ],
  [
    id: 'parentTwo',
    name: 'Parent Two',
    children: ['childOne']
  ],
  [
    id: 'childOne',
    name: 'Child One',
    children: []
  ],
  [
    id: 'childTwo',
    name: 'Child Two',
    children: []
  ],
}]

I could implement something like the above, but with restrictions. e.g. if a child has a second parent, the parent would need to be siblings in the same SkillTreeSegment, and the children would also need to be at the same level.

This could mean that a child could have n-parents, but the positioning of the children becomes a serious issue.

The second would be for a child to have a canonical parent, where it exists under parent's children key, while other parents are able to reference it via a key. But some issues that come to mind is determining the implications of having a canonical parent. Positioning will still be an issue, but at least now the onus of how the tree looks will be placed on the person creating their tree. They'll have the control as to which parent should be the canonical parent, and the placement of any secondary parents.

My dream when creating this package would be for people to easily create skill trees like the one you posted. The difference between having a responsive web app that dynamically creates trees, and creating a static video game tree is that the video-game developer/designer can structure the nodes, edges and trees in any way they please, and have full control in doing so.

I would love to see a proposal or a proof-of-concept. Let me know if you have any thoughts on this as well. You've also given me a bit to think about too! Thanks

[Cyberistic]

If anyone has a working solution, even if it's hacky, please post it.
I need this feature urgently.

[rsinohara]

What about allowing skills to have a parents field, complementary to children. It would be backwards compatible (barring any issue I am missing)? If there is no clear problem, I think I can try this approach.

[maxaug999]

Was anyone able to connect multiple parents ?

[Qwunter]

Same question here, I would love to use this, but I can't at the moment because there is no multiple parents possible.
And with that to chose

• You need both of them to select the skill
• You need at least one of them to select the skill