Thanks for the great extension. This is much faster than the original (and now unmaintained) todo-tree extension, but every time I open VS Code, better-todo-tree needs to re-scan my entire workspace. I frequently switch between workspaces and it's always a hassle to have the tree rebuild every time (my workspace is rather large and contains many files).
I was wondering if it would be possible to create a cache of the tree that can persist between VS Code sessions. The cache can be tied to a specific workspace or folder, and updated whenever the user makes a change inside a VS Code session with that workspace/folder open. Furthermore, perhaps your extension can rebuild the cache from scratch if the previous cached tree is older than some user-defined time (e.g., a few days), and give the user an option/command to force a manual re-build of the tree as well.
Thanks for the great extension. This is much faster than the original (and now unmaintained)
todo-treeextension, but every time I open VS Code,better-todo-treeneeds to re-scan my entire workspace. I frequently switch between workspaces and it's always a hassle to have the tree rebuild every time (my workspace is rather large and contains many files).I was wondering if it would be possible to create a cache of the tree that can persist between VS Code sessions. The cache can be tied to a specific workspace or folder, and updated whenever the user makes a change inside a VS Code session with that workspace/folder open. Furthermore, perhaps your extension can rebuild the cache from scratch if the previous cached tree is older than some user-defined time (e.g., a few days), and give the user an option/command to force a manual re-build of the tree as well.