* Added FOAM_CURRENT_DIR template variable
* Added /research-issue Claude command
* Added integration test to create note using FOAM_CURRENT_DIR
* Updated documentation
* fixed comment
* Fail FOAM_CURRENT_DIR resolution if no editor nor workspace is open
The issue was caused by inconsistent path resolution in NoteFactory.createNote. When templates specified absolute paths like filepath: '/2025-09-05.md', the system was:
1. Checking file existence using the raw template path (filesystem absolute)
2. Creating files using the workspace-resolved path (workspace relative)
This mismatch caused the existence check to fail, leading to template reapplication.
- Template objects
- Separation of template loading, processing and file creation
- Support both Markdown and JavaScript templates
- Somewhat secure VM sandbox for JavaScript template execution in trusted workspaces
- Main entry point for note creation is `create-note` command
- Maintain backward compatibility with existing API
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Added VS Code mock to turn e2e into unit/integration tests
* Provide fallback to editor directory when creating new note with relative path
* Added `clear` function to `FoamWorkspace`
* Fixed tests for dated notes by providing configuration defaults
* Using different workspace directory when resetting mock
* tweaked test suite configuration to manage vscode mock
* Tweaked test scripts to allow running specs in "unit" mode with mock vscode environment
* Marked spec files that can be run in unit mode
* Added testing documentation
* removed --stream flag
* updated @types/node to match engine's version
* Fixing open-resource tests
