d3r nesting order for SearchTree widget

[yonicd]

#Doesnt give the value column in the leaves when branch fully grown
Titanic%>%as.data.frame

#Does give the value column in the leaves when branch fully grown
Titanic%>%data.frame%>%mutate(value=NA)%>%distinct

#Current Call
  #d3_nest doesnt nest in the correct order for ggtree.js making the links float to the last open parent
ggtree(
  list(
    root = d3r::d3_nest(
      Titanic%>%data.frame%>%mutate(value=NA)%>%distinct,
      value_cols = "Freq"
    ),
    layout = "collapse"
  ),
  name = "id",
  value = "colname"
)

#Call with old df2tree function
  #df2tree nests in the correct order for ggtree.js giving a unique parent for each child
ggtree(
  list(
    root=df2tree(Titanic%>%data.frame%>%mutate(value=NA)%>%distinct),
    layout = "collapse"
  ),
  name = "name",
  value = "value"
)

#Compare different nesting orders visually
jsonedit(d3r::d3_nest(
  Titanic%>%data.frame%>%mutate(value=NA)%>%distinct,
  value_cols = "Freq",
  json = F
))

jsonedit(df2tree(Titanic%>%data.frame%>%mutate(value=NA)%>%distinct))

[timelyportfolio]

ok, this is because the node id are not unique, which I believe is more of an issue with the JavaScript, but I'll keep digging.

In my opinion, expecting correct order is an unexpected burden especially on an unsuspecting R user who might not understand scope and reference in JavaScript. Requiring an id (unique) separate from name is probably more robust.

[timelyportfolio]

moving discussion to timelyportfolio/SearchTree#2