There a several more use cases that would benefit from a tree view. For example tags in a knowledge-base(like obsidian) or when using bookmarks plugins. Neo-tree could allow for a uniform "tree-experience" and distinct itself even more from other tree plugins by proving an API to create custom sources.
Describe the solution you'd like.
An API for sources, that allows to pass tree node data in a defined format so that it can be rendered as a custom source.
@pysan3 is doing a pretty large rewrite of the core and I want to say something like this was included in that scope. I will let them confirm or deny this though as I do not remember exactly.
Did you check the docs?
Is your feature request related to a problem? Please describe.
For example current sources are:
https://github.com/nvim-neo-tree/neo-tree.nvim/blob/206241e451c12f78969ff5ae53af45616ffc9b72/README.md?plain=1#L482-L490
There a several more use cases that would benefit from a tree view. For example tags in a knowledge-base(like obsidian) or when using bookmarks plugins. Neo-tree could allow for a uniform "tree-experience" and distinct itself even more from other tree plugins by proving an API to create custom sources.
Describe the solution you'd like.
An API for sources, that allows to pass tree node data in a defined format so that it can be rendered as a custom source.
Describe alternatives you've considered.
No response
Additional Context
No response