You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Code snippets not showing in UI, but total count appears in preferences #729
After opening the app today, the code snippet list is empty (no snippets displayed), but the total number of snippets still shows correctly in Preferences/Statistics. Reinstalling did not fix the issue
Have you tried opening the sidebar to see which folder was selected? Perhaps you deleted the folder, but its selected ID remains in the state as an option.
Have you tried opening the sidebar to see which folder was selected? Perhaps you deleted the folder, but its selected ID remains in the state as an option.
Last week, I adjusted the hierarchy of some folders. When I opened it yesterday, I encountered an issue: all files are still there, but the code snippets are not showing at all. When I tried to create a new code snippet by clicking the "+" button, it seemed to be locked to a specific directory. However, my Vault Path is set correctly.
I'm wondering if this might be a bug caused by adjusting the folder hierarchy. For example, when I move folder A under folder B, the code snippets inside A do not get carried over automatically. As a result, I have to recreate A under B and then delete the original A.
I’m still not sure what exactly it is meant to show, because the right side appears to be Obsidian, not massCode. Could you clarify why Obsidian is included here? Are you only using it to inspect the vault on disk?
Also, the scenario you described earlier, “when I move folder A under folder B, the snippets inside A do not move with it”, does not match what the current implementation is supposed to do. Based on the code, moving a folder should also move its snippet files.
So at the moment I can’t confirm this is the same bug. If possible, please show the massCode sidebar with the selected folder visible and list the exact steps that lead to this state.
Hello @Zhangfen21082. Please describe in detail the sequence of actions that leads to the bug (skip it if it's already there). Add screenshots of errors from the console. If possible add a video. Issues marked with need reproduction will be closed if they have no activity within 3 days.
Activity
antonreshetov commentedon Apr 9, 2026
Have you tried opening the sidebar to see which folder was selected? Perhaps you deleted the folder, but its selected ID remains in the state as an option.
Zhangfen21082 commentedon Apr 9, 2026
Last week, I adjusted the hierarchy of some folders. When I opened it yesterday, I encountered an issue: all files are still there, but the code snippets are not showing at all. When I tried to create a new code snippet by clicking the "+" button, it seemed to be locked to a specific directory. However, my Vault Path is set correctly.
I'm wondering if this might be a bug caused by adjusting the folder hierarchy. For example, when I move folder A under folder B, the code snippets inside A do not get carried over automatically. As a result, I have to recreate A under B and then delete the original A.
antonreshetov commentedon Apr 9, 2026
Thanks for the extra screenshot.
I’m still not sure what exactly it is meant to show, because the right side appears to be Obsidian, not massCode. Could you clarify why Obsidian is included here? Are you only using it to inspect the vault on disk?
Also, the scenario you described earlier, “when I move folder A under folder B, the snippets inside A do not move with it”, does not match what the current implementation is supposed to do. Based on the code, moving a folder should also move its snippet files.
So at the moment I can’t confirm this is the same bug. If possible, please show the massCode sidebar with the selected folder visible and list the exact steps that lead to this state.
github-actions commentedon Apr 9, 2026
Hello @Zhangfen21082. Please describe in detail the sequence of actions that leads to the bug (skip it if it's already there). Add screenshots of errors from the console. If possible add a video. Issues marked with
need reproductionwill be closed if they have no activity within 3 days.