Indeed. Put Enum.sort() in the pipe in produce/0 immediately after Enum.map.
mudasobwa
Creator of Cure
hscspring
Bingo, that’s it.
and there is a very little error in the output
# the output
%TestNode{
children: %{
"" => %TestNode{
children: %{
"2" => %TestNode{
children: %{
"3" => %TestNode{
children: %{
"5" => %TestNode{children: %{}, path: "/2/3/5"},
"7" => %TestNode{children: %{}, path: "/2/3/7"},
"8" => %TestNode{children: %{}, path: "/2/3/8"}
},
path: "/2/3"
},
"4" => %TestNode{
children: %{"6" => %TestNode{children: %{}, path: "/2/4/6"}},
path: "/2/4"
}
},
path: "/2/3"
}
},
path: "/2/3"
}
},
path: nil
}
for a better view, i did some change to the below
%TestNode{
children: %{
"" => %TestNode{
children: %{
"2" => %TestNode{
children: %{
"3" => %TestNode{children: %{},path: "/2/3"},
"4" => %TestNode{children: %{},path: "/2/4"}},
path: "/2/3"}
},
path: "/2/3"
}
},
path: nil
}
as we see, the right structure may like this
%TestNode{
children: %{
"2" => %TestNode{
children: %{
"3" => %TestNode{children: %{},path: "/2/3"},
"4" => %TestNode{children: %{},path: "/2/4"}},
path: "/2"
}
},
path: nil
}
I’m trying to fix it.
as this approach has adjusted the default order, i will try to sort them when traveling.
0
mudasobwa
Creator of Cure
result.children[""] would return what you want. There’s always 1 root, so it’s safe.
And path somewhere should be set more accurately, yes.
0
hscspring
So it is.
Actually your code is advanced and professional, i’m trying to understand it~
Many thanks to u. Best wishes ~
1
Qqwy
TypeCheck Core Team
An interesting alternative solution. To make it more readable, I’d suggest writing it as
keys =
path
|> String.split("/")
|> Enum.map(&Access.key(&1, %{}))
put_in(tree, keys, %{})
Cool!
I do have trouble understanding what you mean with the shrugging emoji. Could you elaborate? 
0
mudasobwa
Creator of Cure