Implement `foam.files.include` configuration to allow users to specify which files/directories Foam should include.
Also migrating `foam.files.ignore` to `foam.files.exclude`
Fixes#1422
* Added setting to automatically convert wikilinks into md links on insertion/completion
* Improved Position mock and added mock for `extensions` namespace
Fixes#1464
* Support for image embed parameters (e.g. ![[img.png|300|center]])
Resolves#1328
Examples:
![[image.png]] // Original
![[image.png|300]] // Width only → 300px
![[image.png|50%]] // Percentage → responsive
![[image.png|300x200]] // Width × height
![[image.png|20em]] // With units
![[image.png|300|center]] // With alignment
![[image.png|300|Alt text]] // With alt text
* Documentation for image styling
* Add support for title in image links (#1262)
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Tag Peek References:
- Users can now peek all references of a tag
Enhanced Tag Search:
- Created new "Foam: Search Tag" ('foam-vscode.search-tag') command for workspace tag search
- Added inline search action button that appears on hover over tag items in tag explorer
- Clicking search icon triggers VS Code's search panel with tag query
FoamTags to use Location instead of URIs
Implements support for searching note aliases using VS Code's "Go To Symbol in Workspace" command (Ctrl+T/Cmd+T).
Resolves#1461
- Complements VS Code's built-in markdown symbol support (doesn't add symbols for sections)
- On-the-fly computation without caching for simplicity (will review if performance becomes an issue)
- Subsequence query matching following VS Code recommendations
Resolves#1505
When using root-path relative links (e.g., `[text](/path/file.md)`),
Ctrl+clicking would create new notes instead of opening existing files.
This was caused by the markdown provider treating workspace-relative
paths as filesystem absolute paths.
**Changes:**
- Enhanced MarkdownResourceProvider to accept workspace roots context
- Updated link resolution logic to handle workspace-relative paths correctly
- Modified extension initialization to pass VS Code workspace folders
- Enhanced createTestWorkspace() utility to support workspace roots testing
**Behavior:**
- Links starting with `/` now resolve against workspace roots first
- Falls back to existing absolute path behavior when no workspace roots
- Supports multiple workspace scenarios and fragments
- Maintains full backward compatibility
- Adds FOAM_DATE_DAY_ISO to variable resolver
- Adds dedicated and integrated tests for FOAM_DATE_DAY_ISO
- Updates documentation to describe FOAM_DATE_DAY_ISO usage and behavior
