4 ms·
Very sad to discover that this is NOT a ready made component to display actual trees. What a deceitful name! Jokes apart, nice library. Will try it out sooner
by yuchi 5y ago
Very sad to discover that this is NOT a ready made component to display actual trees. What a deceitful name!
Jokes apart, nice library. Will try it out sooner or later. May I suggest to not use children as the prop to Ps the Node component? Maybe a more explicit NodeComponent prop would have been better imho.
- pjerem 5y ago> Very sad to discover that this is NOT a ready made component to display actual trees. What a deceitful name! Hey, since you get to decide the structure yourself, I’m sure you could use that to draw a real tree using SVG.
- jameskerr 5y agoDang it, I can see how the title was deceptive. This is headless component, leaving the markup and styling completely up to the user. Many of the tree components I looked at before building this didn't let me do exactly what I wanted with the style like this one does. However, I was thinking of shipping a default "<Item>" component that comes with some default styling to get people up and running quickly. I've just made an issue for this.
- gedy 5y agoThis is really great that it's headless btw, so many react components hard-code style that it's makes them difficult to use in another design system
- jameskerr 5y agoI felt this same pain and it was one of main motivations to make this library.
- bredren 5y agoIf anything, it would be great to see some of the other components you’ve styled for this. The behavior is important but the visuals sell.
- searchableguy 5y agoI think I would much prefer a documentation page going through styling the headless component vs ready made styled component with basic styles. This is the approach used by most headless projects such has headless ui or radix.