Gruntfuggly / todo-tree

Use ripgrep to find TODO tags and display the results in a tree view
Other
1.43k stars 139 forks source link

Issues with Global Storage Folder with Roaming Profiles #823

Open punkfac3kid opened 7 months ago

punkfac3kid commented 7 months ago

I am currently attempting to troubleshoot out a user's interactions with the todo-tree extension from within VS Code while operating on a roaming profile setup in a virtual infrastructure.

To my knowledge up to this point a lot of the VS Code pathing to remote storage locations has worked fine with the baked in Windows variables, ie. %APPDATA%\Code\..., with the exception now of todo-tree. Whenever we attempt to use it with all of our other settings roaming to an alternate location outside the scope of the normal APPDATA that lives on the C: drive it seems that todo-tree doesn't elaborate a full path.

For example, the current path for the code folder shows up on a file server that is normally accessed by a UNC path. All settings for Code itself work. When you add a TODO flag in a file and then save; nothing is displayed on the todo tree itself in the side pane. The debug log shows it found the flag and in what file, plus the full path to it; but the last line is Attempting to create global storage folder \folder_root\username\AppData\Code\User\globalStorage\gruntfuggly.todo-tree. The weird thing about this is it is completely stripping out the UNC modifier to the front. That folder definitely exists, but because it is ignoring the specifier for the \\SERVERNAME before the root folder it is not finding it.

Is there already a way to point this somewhere with an explicit path such that we can workaround it or am I just crazy and missing something?