Todo list in tree view

[lewislepton]

just a request if possible. that the list could be put at the sidebar, under the source code portion. ill give a screenshot just to show where just in case ;)

great package though, really useful ;)

[mrodalgaard]

I have been thinking about making a compact mode in a panel. Might also be able to put it in the lower part of the tree view if space or scalable. But this will take a lot of work to implement.

[nonameolsson]

Would be a nice feature!

[dmig]

Would be very useful enhancement! Current table view is bloated and a space-waster

[BuonOmo]

Maybe just a tree view in place of the table view (with an option on which to prefer) would be nice already. Like todo package

[brettz9]

I was thinking it might also be interesting to leverage the format of https://github.com/sindresorhus/eslint-plugin-unicorn/blob/master/docs/rules/expiring-todo-comments.md which would make a tree view even more interesting, as one could change the table into a tree using not only the files as the main branches, but optionally also other aspects of the to-dos (e.g., their expiration date).

Though Unicorn wasn't interested in the bulk of my proposals for expanding their rule, I wonder if it would be in the scope of your package, particularly the ability to parse a to-do for a particular structure so as to discover features like dates priority and/or scope information (e.g., // todo (testing=5) for a to-do whose scope is for "testing" and which is a level 5 priority), and even to allow further nesting of to-dos according to an arbitrary hierarchy, e.g., // todo (testing.mocha.modules): Switch to ESM. The hierarchy could thus be organized by priority or by scope--including nesting scopes (e.g., "modules" within "mocha" within "testing" to-dos).

I'd even find this useful from within Markdown files, as I'd sometimes like to view to-dos according to their concept (e.g., all of my refactoring to-dos together), and sometimes for their need for immediacy/priority.