test: last tree node is a subtree

[caarlos0]

this is currently resulting in

        ├── Foo
        ├── Bar
        │  ├── Qux
        │  ├── Quux
        │  │  ├── Foo
        │  │  └── Bar
        │  └── Quuux

not sure how to best fix it, though...

I think maybe the api needs be a bit different, e.g., instead of:

New("foo", New("bar", "zaz", New("aa"))

something like:

New(New("foo", "bar", New("zaz", "aa")))

This is also what I was kinda expecting: the first param is the node name, and the remaining are its children.

It would also make a bit more sense in internal semantics, as currently the children of a node can be either the next nodes or a subtree, which IMHO is the thing that should be called children.

thoughts?

[caarlos0]

last commit:

• fixes last node of the tree being a subtree
• allows for a tree to have a name and children
• fixes other bugs found
• changes the rendering so instead of rendering per line, it renders an slice of nodes directly
• changes New signature to take a name and an slice of children Node implementations
• adds a StringNode type alias/Node implementation
• renames the old StringNode to TreeNode

[maaslalani]

We’ll need to double check that multi-line elements show up correctly, that way we can embed lists within trees, which was the reason for the tree abstraction

[caarlos0]

superseeded by #264

[caarlos0]

closing in favor of #264