Worked on si4k’s Diary (VS Code extension) stability + UX polish.
#What I did today
- Command wiring + activation fixes
- Verified command registrations and ensured the extension activates reliably when running
si4ksDiary.*commands.
- Verified command registrations and ensured the extension activates reliably when running
- Diary explorer refresh + filesystem watching
- Added/updated
.diary/**/*watchers so the tree view refreshes after create/edit/delete. - Triggered both custom tree refresh + native Explorer refresh (best-effort) after actions.
- Added/updated
- Entry/template creation flow improvements
- “Create file” prompts for a name first (no auto-file on
+), then asks for template. - Kept “New Entry with Template” flow aligned with form-like templates.
- “Create file” prompts for a name first (no auto-file on
- Template file editing
- Templates can be opened as editable files so users can tweak them directly.
- MongoDB URI pain points
- Investigated connection errors (
querySrv ENOTFOUND …) and improved validation guidance. - Noted the special case where passwords containing
@can confuse naive parsing.
- Investigated connection errors (
#Current status
- The extension reports “folder/file created”, but new items still aren’t reliably showing in the diary sidebar in some cases likely a provider refresh / path resolution / scan mismatch issue that needs deeper debugging tomorrow.
0
Log in to leave a comment