Behavior of getPathNodes

[JaySunSyn]

@plequang Assuming, we have this tree:

{
    "2": {
        "id": "167d1485-7d4f-4c7d-86cd-a4fb00f31245",
        "name": "Node2",
        "pathLocator": "1.2",
         "children": {
            "601": {
                "id": "865065da-yyf44c-472e-a8df-a4fb00f3124b",
                "name": "Node401",
                "pathLocator": "1.2.3.2.601",
                "children":  {
                    "401": {
                          "id": "865065da-xxf44c-472e-a8df-a4fb00f3124b",
                           "name": "Node601-401",
                           "pathLocator": "1.2.3.2.601.401",
                           "children": {}

                }

            }
    },

    "301": {
        "id": "3a7654f1-e3e6-49c7-b6a8-a4fb00f31245",
        "name": "Node301",
        "pathLocator": "1.2.3.301",
        "children": {
            "401": {
                "id": "865065da-f44c-472e-a8df-a4fb00f3124b",
                "name": "Node401",
                "pathLocator": "1.2.3.301.401",
                "children": {
                }

            }
        }
    }
}

We should discuss following (and more?) scenarios:

• 1.2 => [2]
• 401 => 401 is a node in both roots, 301 and 2. Which one to take? or None?
• 301.99.401 => Take the one with most defined nodes? In case root 2: [undefined, undefined, 401] In case root node 301: [301, undefined, 401]. Or fail after undefined?

Also see discussions of #1
especially here #1 (comment)

[JaySunSyn]

Fixed with #6