bueckerlars_obsidian-note-mover-shortcut/CHANGELOG.md

Changelog

1.2.0

Features

• Conflict resolution when the destination already exists (#25): Moves that would collide with an existing file at the target path are handled by a configurable strategy — Ask every time (ConflictModal with skip, rename, or overwrite; optional “Always use this choice” persists the strategy), Always skip, Always rename (numeric suffix such as note (1).md), or Always overwrite. New Settings → Conflict resolution section selects the default (Always skip for new installs and when no strategy was saved yet). A skip cache remembers skipped source/target pairs so batch moves and vault re-evaluation do not re-prompt for the same conflict. Concurrent moves to the same target path are serialized with per-path locking. Notices report when a file was skipped, renamed to avoid a conflict, or overwrote an existing file.
• Optional destination folder creation (#103): New toggle under Settings → Rules — Create missing destination folders (on by default). When disabled, notes are not moved if the target folder does not exist; a warning notice explains why (on-edit and manual moves). Each rule can override the global default in the rule editor (Use global default, Always create, or Never create). Bulk, periodic, and preview completion notices summarize how many files were skipped because the destination folder was missing.

Fixes

• Bulk and periodic skip summaries: Move-all and periodic runs now report skipped files in the completion notice — separately for missing destination folders and for conflict skips (including cached conflict skips) — even when no files were moved.
• Preview vs runtime folder checks: Rule preview uses the same adapter.exists folder check as move execution, so preview and runtime agree on whether a destination folder exists.

1.1.2

Fixes

• Release notes on vault switch and mobile restart (#92): lastSeenVersion is now stored at app level (localStorage) in addition to vault data.json, so the changelog modal is not shown again when switching vaults or after force-stopping Obsidian. Version is persisted before the modal opens to reduce repeat prompts when vault saves are interrupted on mobile.

1.1.1

Fixes

• Minimum Obsidian version on mobile (#95): Corrected minAppVersion from 1.13.0 to 1.8.7 so the plugin is offered again in Community Plugins on Obsidian 1.12.x (iOS/Android). Releases v1.0.5–v1.1.0 were not installable on those builds because they required a newer Obsidian than currently available on mobile.

1.1.0

Features

• Vault re-evaluation after rule changes (#80): New command Re-evaluate entire vault with current rules and a matching button under Settings → Rules. Syncs the latest rules, clears the evaluation cache, opens a preview of planned moves, and only moves files when you confirm in the modal.
• Date components in destination templates (#98): Property placeholders now support date components such as {{property.created.year}}, {{property.created.month}}, {{property.created.monthName}}, and {{property.created.dayOfWeek}} for building folder paths from date frontmatter without separate year/month fields.

Fixes

• Rule editor footer: Save, Cancel, and Remove rule buttons were rendered but often invisible or not clickable on desktop because the footer used Obsidian Setting wrappers without a label, leaving an empty .setting-item-info that broke the layout. The footer now uses BaseModal button helpers (same pattern as the preview modal), so all actions are visible and clickable again.
• Remove rule in editor: Deleting a rule from the editor footer works again — confirm dialog, removal, and list refresh.
• Rule evaluation cache after rule edits: Saving, deleting, or toggling a rule in settings now calls updateRuleManager(), so the in-memory rule engine and evaluation cache stay in sync with your saved rules (previously only clone and reorder did this).

Improvements

• Unsaved changes guard: Closing the rule editor with unsaved edits (Cancel, X, or Esc) shows a confirmation dialog before discarding changes.
• Sticky rule editor footer: Action buttons stay reachable when editing rules with many conditions.

1.0.6

Fixes

• Plugin review feedback: Address Obsidian community plugin review findings — confirmation dialogs no longer use innerHTML; messages are rendered with MarkdownRenderer. DOM access uses activeDocument, notices use Notice.messageEl, and async handlers use explicit void where fire-and-forget is intended.

Improvements

• Sentence-case UI: Settings and modals follow Obsidian sentence-case guidelines (e.g. "Match conditions", "Import/export", "+ add rule", "Add to blacklist").
• Confirmation dialogs: Clear-history, import, and delete-rule prompts use Markdown (rule names in inline code). Destructive actions use setDestructive() instead of warning styling.
• Modal sizing: Desktop modal dimensions are applied on modalEl in BaseModal instead of global CSS size classes, keeping layout scoped and compatible with Obsidian ESLint rules.
• Settings persistence: History save/load and settings validation use typed PluginData / SettingsData instead of any casts; migration logs use console.debug.
• Minimum Obsidian version: Raised to 1.13.0 (manifest.json / versions.json).
• Dev tooling: ESLint 9 flat config with eslint-plugin-obsidianmd, GitHub Actions CI (lint, type-check, tests), and changelog generation before lint/type-check and in CI.

1.0.5

Fixes

• Release notes on every startup (#92): The update changelog modal no longer opens on every Obsidian start when lastSeenVersion was missing or stored only under settings. It now appears only after the installed plugin version is newer than the last seen version. Legacy lastSeenVersion values nested in settings are migrated to the root PluginData field and saved immediately so the migration does not repeat on each load.

Improvements

• Show release notes after plugin update (#92): New toggle under Settings → Updates (on by default). Turn it off to skip the changelog modal after updates; the plugin still records the current version quietly.

1.0.4

Improvements

• Move confirmation toasts (#86): Single-file moves (command, ribbon icon, and on-edit trigger) now show a success notice when a note is actually moved, e.g. "My Note" moved to tasks/personal. No toast when no rule matched or the file was already in the target folder.

1.0.3

Fixes

• Canvas tag and content rules (#76): Tag, property, link, heading, and embed criteria now apply to .canvas files by aggregating metadata from text cards on the board (inline #tags, frontmatter, wikilinks) and from file cards that reference vault notes. The canvas file itself is still what moves when a rule matches—matching the workflow of creating a note on the canvas and routing the canvas by its card content.

1.0.2

Fixes

• Modal layout regressions (#88): CSS lint cleanup replaces !important and :has with scoped selectors, restores modal sizing via modalEl, and aligns preview footer buttons without Setting wrappers.

Improvements

• Release artifact attestations (#89): The GitHub release workflow now attests main.js and styles.css for supply-chain verification.
• Dev tooling refresh (#87): Replaced deprecated dev dependencies with lighter alternatives (lint-staged → nano-staged, builtin-modules → Node builtinModules) and updated the lockfile.

1.0.1

Fixes

• Nested tag matching for rules (#83): Tag triggers now use hierarchical matching for parent/child tags. A rule for #tag matches #tag and nested tags like #tag/tag1, but not sibling-prefix tags like #tag1. This applies to includes item, does not include item, all start with, and none start with for tag criteria. Blacklist tag matching now shares the same hierarchy logic to keep behavior consistent.

1.0.0

Breaking

• Rebranding to "Advanced Note Mover": The plugin has been renamed from NoteMover Shortcut to Advanced Note Mover. The internal plugin ID (note-mover-shortcut) is unchanged so existing installations and settings keep working and continue to receive updates. Public classes were renamed accordingly: NoteMoverShortcutPlugin → AdvancedNoteMoverPlugin, NoteMoverShortcut → AdvancedNoteMover, NoteMoverShortcutSettingsTab → AdvancedNoteMoverSettingsTab. CSS class prefixes changed from noteMover- to advancedNoteMover-; custom CSS snippets targeting the old prefix must be updated.
• Legacy Rule V1 removed: V1 rule types, legacy settings toggles, and duplicate mobile-only settings/modal implementations were dropped. Existing V1 rules are still migrated once on load (with backup) into Rule V2.

Features

• Canvas and Base movement (#76): Commands, bulk/periodic scans, preview, and on-edit triggers now move Canvas (.canvas) and Base (.base) files in addition to Markdown notes. Active-file commands appear when a canvas or base file is focused. For these file types, prefer fileName, folder, or extension rules—tag, property, link, and heading criteria usually do not apply (Obsidian’s metadata cache is markdown-oriented).
• Move attachments with note (#77): Optional co-move of referenced attachment files in the note folder subtree when a markdown note is moved (preserves relative paths such as _assets/). Configurable in Settings → Attachments; off by default on upgrade, on for new installs. Undo restores co-moved attachments.
• Preview bulk cancel: While executing moves from the preview modal, you can Stop the remaining renames; completed moves stay in history.

Improvements

• Rule evaluation cache on by default for new installs and unset data; existing false stays respected.
• Lazy vault.read for filters: If a blacklist line uses content:, file body is read for that evaluation path only.
• Regex warmup: Rule V2 regex patterns are precompiled when rules are loaded.
• Bulk throughput: Chunked vault moves and preview execution use requestIdleCallback when available instead of only setTimeout(0).
• Application services: Thin MoveFileService, PreviewService, and HistoryService facades on the plugin (appServices) for clearer layering.
• README: Documented blacklist-only filters and Rule V2-first configuration (removed outdated whitelist / V1 criteria wording).

0.7.1

Features

• Template-based destinations: Destinations can now include tag and property placeholders such as {{tag.tasks/personal}} and {{property.status}} to dynamically build target folders from note metadata.
• Template suggestions in destination inputs: Destination inputs use an enhanced suggester that offers completions for {{tag.*}} and {{property.*}} placeholders based on tags and properties discovered in your vault.

Improvements

• Rule editor UX: Updated desktop and mobile rule editor destination inputs, descriptions, and placeholders to highlight template support and provide clearer examples.
• Changelog rendering: The in-app update modal now renders changelog list entries as Markdown, so formatting and links from the changelog are displayed correctly.

0.7.0

Features

• Rules V2 as default: Rules V2 is now the default rule system. The previous "Enable Rule-V2 (beta)" toggle has been replaced by Enable Legacy Rules (V1) in a new "Legacy" settings section at the bottom of the settings. New users get Rules V2 by default; existing users keep their current behavior via automatic migration of the enableRuleV2 setting to enableLegacyRules (inverted).
• Legacy Migration Modal: When using Legacy Rules (V1) with at least one rule and the prompt has not been dismissed, a modal appears on load offering: Migrate to Rules V2 (migrates rules and switches to V2), Ask me later, or Don't ask again (persisted via legacyMigrationDismissed). Desktop and mobile layouts are supported with appropriate styling.

Improvements

• Settings UI: Removed the "Enable Rule-V2 (beta)" toggle from the Rules section. Legacy mode is now controlled from the dedicated "Legacy" section (desktop and mobile).
• Import/Export: Export and import now use enableLegacyRules and legacyMigrationDismissed. Imports that still contain enableRuleV2 are converted to enableLegacyRules (inverted) for backward compatibility.
• Deprecation clarity: RuleManager, RuleMatcher, Rule (V1), and MobileRuleItemV1 are explicitly documented as legacy; RuleV2/RuleManagerV2 remain the default and recommended path.
• Performance for large vaults: Several optimizations to reduce work and improve responsiveness when many files are present.
  • Suggesters: Added 500ms debouncing and lazy loading to AdvancedSuggest and PropertySuggest to avoid repeated full vault scans on metadata changes. FolderSuggest now caches the folder list and exits early when the suggestion limit is reached.
  • Metadata extraction: V1 MetadataExtractor skips vault.read() when no content-based rules exist. V2 MetadataExtractor no longer calls getFileCache() twice.
  • Rule matching: V1 RuleMatcher uses early-exit loops and a regex cache.
  • Preview modal: Reuses pre-computed target paths instead of re-evaluating rules.
  • Bulk moves: Chunked processing with UI yielding to keep the interface responsive during large move operations.

Fixes

• RuleV2 property repair: Repair of RuleV2 properties with missing propertyName now runs when in Legacy mode but rulesV2 data exists (e.g. after re-enabling Legacy), so validation errors are avoided in that case.

0.6.0

Features

• Rule Evaluation Cache (beta): Added an opt-in caching layer that tracks which files have changed between rule checks, skipping redundant re-evaluation for files already in their correct folder. On periodic runs this reduces work from O(all files) to O(changed files). Enable via the new toggle in the Triggers settings section.

Bug Fixes

• Periodic Trigger Notice: Fixed the periodic trigger always showing "Successfully moved X files" even when no files were actually moved. The move count now only reflects files that were truly relocated.

Improvements

• V2 Metadata Extraction Optimization: extractFileMetadataV2() no longer reads full file content via vault.read(). V2 rules only use metadata cache fields (tags, links, properties, etc.), so the costly I/O call is now skipped entirely.

0.5.9

Improvements

• Enhanced RuleV2 Property Repair: Improved property repair functionality in RuleMigrationService
  • Added getDefaultOperatorForPropertyType function for intelligent operator selection based on property types
  • Better operator selection when extracting property values from corrupted data
  • Improved handling of extracted values to ensure operators match property types (text, number, date, list)
  • Enhanced value type safety with ensureStringValue helper to handle corrupted data types

Fixes

• Fixed rule manager not updating after cloning rules
  • Rule manager now properly updates after cloning rules in both desktop and mobile settings
  • Ensures cloned rules are immediately available for file movement operations
• Fixed duplicate RuleV2 property repair execution
  • Property repair now only runs once when RuleV2 is enabled, preventing unnecessary duplicate repairs
  • Improved conditional logic to prevent repair execution when RuleV2 is already enabled

0.5.8

Features

• Rule Cloning: Added ability to clone rules in both desktop and mobile settings
  • Clone button available in RulesSettingsSection (desktop) and MobileRulesSection (mobile)
  • Cloned rules are automatically named with "(copy)" suffix and inserted directly after the original rule
  • Simplifies creating similar rules with minor variations

Improvements

• Enhanced Rule Migration: Improved RuleV1 to RuleV2 migration with better validation and error handling

  • Added operator validation against criteria types and property types during migration
  • Improved value processing to preserve important leading characters (e.g., # for tags)
  • Better handling of empty values for operators that require values
  • Enhanced logging for migration process with detailed warnings and errors
  • Improved date criteria handling with appropriate default operators

• RuleV2 Property Repair: Added automatic repair functionality for RuleV2 properties

  • Automatically repairs properties triggers with missing or empty propertyName fields
  • Extracts property name from value when possible (supports both "key" and "key:value" formats)
  • Disables rules that cannot be repaired to prevent validation errors
  • Runs on plugin startup to ensure data integrity

Fixes

• Fixed RuleV2 migration issues with property criteria
  • Properly handles property criteria with and without values
  • Correctly sets operators based on whether property has a value or is existence-only
  • Fixed date criteria operator selection to use appropriate defaults

0.5.7

Fixes

• Fixed rule validation

0.5.6

Improvements

• Mobile-First Redesign of RuleEditorModal: Complete mobile optimization of the rule editor modal
  • Introduced reusable mobile modal components (Card, Input, Toggle, Button, Section) for consistent UI/UX
  • Implemented MobileTriggerCard component with card-based layout for trigger conditions
  • Separated mobile and desktop implementations, removing all conditional mobile logic
  • Replaced SVG strings with setIcon() for better maintainability
  • Optimized CSS with consistent padding (16px horizontal, 12px card padding) and touch-friendly targets (min-height: 48px)
  • Mobile UI now uses a consistent design system matching the mobile settings interface

0.5.5

Fixes

• Fixed CSS selectors overwriting global Obsidian styles #48
  • Scoped .vertical-tab-content selector to plugin containers only
  • Restricted .setting-item-control selectors to plugin modals and containers
  • Limited generic button selector to plugin elements only
  • Prevents plugin styles from affecting other Obsidian UI elements, especially on mobile devices

0.5.4

Fixes

• Refactored mobile styles and classes for improved consistency
  • Updated CSS class names to follow a unified naming convention with the prefix 'noteMover-' for better organization
  • Refactored modal and settings components to utilize the new class names, enhancing mobile responsiveness and usability
  • Ensured all mobile-specific styles are applied consistently across various modals and settings sections
  • Updated drag & drop functionality, suggesters, and all mobile components to use the new naming convention

0.5.3

Fixes

• Fixed RuleV2 toggle on mobile not updating the active rule manager
  • When toggling RuleV2 on mobile, the code now properly calls updateRuleManager() to initialize the correct rule manager
  • Prevents file movement operations from using an uninitialized rule manager after toggling the feature flag

0.5.2

Features

• Conflict Resolution: Prevent file overwriting when target file already exists #25
  • Files with conflicts are automatically skipped during move operations
  • Warning notices are displayed for skipped files
  • Batch operations show summary of moved, skipped, and failed files
  • Works for both RuleV1 and RuleV2 systems
• Enhanced mobile UI responsiveness with optimized layouts for all modals
  • Mobile-specific button layouts with vertical stacking and full-width buttons
  • Improved touch targets with minimum 48px height for better usability
  • Mobile-optimized preview modal with vertical path display
  • Enhanced history modal with mobile-friendly button layouts
  • Mobile-specific styling for confirm, update, and rule editor modals

Improvements

• Added automatic scroll position reset when modals open
• Implemented mobile detection utilities for consistent mobile experience
• Enhanced modal sizing with mobile-specific full-width layout
• Improved accessibility with larger touch targets and better spacing on mobile devices

0.5.1

Features

• Improved UI responsiveness #48

0.5.0

Features

• RuleV2 System (Beta): Complete rewrite of the rule matching system with advanced trigger-based logic
  • New Criteria Types: Support for fileName, folder, extension, links, embeds, headings, properties, created_at, modified_at
  • Advanced Operators: Type-specific operators for text, list, date, and property matching
    • Text operators: is, contains, starts with, ends with, match regex
    • List operators: includes item, all are, any contain, count is, etc.
    • Date operators: is before/after, date is today, is under X days ago, component matching
    • Property operators: Runtime type-checking with support for text, number, checkbox, date, and list properties
  • Aggregation Logic: Support for all, any, and none aggregation modes across multiple triggers
  • Feature Flag: Toggle between RuleV1 and RuleV2 systems via enableRuleV2 setting
  • Backward Compatibility: RuleV1 system remains fully functional when RuleV2 is disabled
  • Performance Optimizations: Regex caching, efficient metadata extraction, and optimized matching algorithms

Changes

• Metadata Extraction: Enhanced MetadataExtractor with V2-specific fields (extension, links, embeds, headings)
• Rule Management: New RuleManagerV2 class with advanced preview and validation capabilities
• Type Safety: Full TypeScript type safety with CriteriaType-to-Operator mapping
• Error Handling: Graceful handling of invalid regex patterns and malformed data

0.4.7

Features

Changes

• Marked NoteMoverSettings interface as deprecated
• Refactoring to use the new PluginData interface

Fixes

• Fixed SettingsValidator to accept both deprecated and new settings data structure
• Enabled notifications on periodic movements
• Improved performance of On-Edit Trigger

0.4.6

Features

• Added Add current file to blacklist command.
• Added new action button on history entries to add the file to blacklist

Changes

• Removed FilerMode setting and reworked filter logic to work always if mode is set to blacklist

0.4.5

Fixes

• Rule Matching: RuleMatcher now leverages MetadataExtractor to support list-property matching via parseListProperty/isListProperty.
• Debounced Rendering: Introduce DebounceManager; SettingsTab refreshes via debounced display() and provides cleanup().
• Memory Safety: FilterSettingsSection/RulesSettingsSection track AdvancedSuggest instances and DragDropManager; added cleanup() and proper refresh after DnD save.

0.4.4

Features

• Implemented check if note is in the correct folder already before move
• Implemented drag&drop reordering for rules and filters

Bug Fixes

• Fixed skipping of already moved files
• Fixed filter blacklist for folders #33

0.4.3

Changes

• Removed onlyMoveNotesWithRules setting

Fixes

• Bulk moves skip notes that are in the correct folder already

Improvements

• The UpdateMangager gets a dynamic on build-time generated changelog instead of a copy from the CHANGELOG.md

0.4.2

Features

• Added an option for "on-edit" note movement
• Changed the filter whitelist/blacklist toggle to a dropdown

Changes

• Renamed the periodic movement settings section to trigger section
• Implemented an event system for periodic movements and on-edit movement

0.4.1

Attention: Breaking Changes

Changes

• Removed inbox and notes folder settings
• Added setting for history rentention policy and dropdown in the history modal to select timespan of the entries shown

0.4.0

Features

• Added a button for opening notes in the History Modal
• Added Wildcard and Regex matching for filenames in the rules
• Added Settings for importing and exporting settings

Changes

• Implemented comprehensive codebase refactoring for improved maintainability and performance
• Added new FileMovementService class for unified file movement operations
  • Centralized file movement logic with plugin move tracking
  • Enhanced folder creation and batch operation support
  • Improved error handling and history integration
• Introduced MetadataExtractor class for standardized file metadata access
  • Efficient extraction of file metadata, tags, and frontmatter properties
  • Optimized performance for large vaults with caching mechanisms
• Created new RuleMatcher class for advanced rule and filter matching
  • Hierarchical tag matching with specificity-based rule sorting
  • Enhanced wildcard pattern matching for file names
  • Improved frontmatter property evaluation
• Added BaseModal class for consistent modal UI across the plugin
  • Standardized modal creation and styling
  • Improved user experience with consistent design patterns
• Implemented NoticeManager class for unified notification system
  • Customizable notice types with undo functionality
  • Enhanced error reporting and user feedback

Improvements

• Refactored all modal classes to extend BaseModal for consistency
• Enhanced error handling with standardized error creation and management
• Improved test coverage with comprehensive unit tests for new classes
• Added configuration constants for better maintainability
• Optimized suggestion systems with improved metadata extraction
• Enhanced path utilities with new helper functions
• Improved code organization and separation of concerns

Bug Fixes

• Fixed various edge cases in file movement operations
• Improved error handling for folder creation failures
• Enhanced undo functionality for complex file operations
• Fixed issues with metadata extraction in edge cases

0.3.4

Features

• Added "Only move notes with rules" option #21
  • New toggle in Rules settings to control note movement behavior
  • When enabled: Only notes matching defined rules will be moved, others remain untouched
  • When disabled: Notes without matching rules are moved to the default destination folder
  • Provides flexibility for users who want selective note processing based on rules

Improvements

• Enhanced rule processing logic to support selective note movement
• Updated preview functionality to reflect the new movement behavior
• Improved user experience with clear option descriptions and conditional UI display

0.3.3

Features

• Implemented file move preview functionality to show which files will be moved before execution
• Added bulk undo functionality to history for reverting multiple movements at once
• Added custom confirmation modal

Bug Fixes

• Fixed bug where undo was failing with notes that are moved to subfolders by rules
• Small styling fixes for preview modal

Improvements

• Enhanced test coverage and improved mock data in tests

0.3.2

Features

• Added support for Properties (Frontmatter) in Rules and Filters #20
  • New property: criteria type for filtering and moving notes based on frontmatter metadata
  • Support for exact value matching (property:key:value) and existence checking (property:key)
  • Case-insensitive property value comparison with support for different data types
• Enhanced property suggestions with three-level autocomplete
  • Intelligent suggestion hierarchy: type → property key → property value
  • Auto-completion of property keys and values from vault analysis
  • Seamless UX with automatic colon insertion after property key selection

Improvements

• Extended AdvancedSuggest with comprehensive property value tracking
• Updated UI placeholders and descriptions to include property examples
• Added comprehensive test coverage for property-based functionality

0.3.1

Features

• Implemented support for subtags in rules #19
• Implemented creation of destination folders that do not exist when moving notes

0.3.0

Features

• Implemented update modal that shows changelog information for new versions
• Added advanced filter system with intelligent suggestors for folders and tags
• Implemented advanced suggest system for rule settings
• Added automatic history event listener for tracking manual file operations
• Command to manually show update modal for viewing changelog

Improvements

• Refactored rule code to make iterations and maintenance easier
• Improved test coverage and updated test implementation for new filter settings
• Enhanced user experience with better autocomplete suggestions

0.2.1

Bug Fixes

• Fixed config gets overwrited on history changes #17

0.2.0

Features

• Implemented movement history
• Added modal to show the history and revert movements
• Added Notice for single move command with undo option

0.1.7

Bug Fixes

• Fixed issues mentioned in PR obsidianmd/obsidian-releases#6028

0.1.6

Bug Fixes

• Removed path import for mobile support
• Refactored suggestors with AbstractInputSuggest
• Use getAllTags() method for getting tags to insure tags are used from file and frontmatter
• Fixed UI texts with sentece case
• Removed use of innerHTML from log functions

0.1.5

Features

• Added periodic movement options to settings
• Implemented timer function
• Added filter options to settings
• Added heading to periodic movement setting
• Implemented filter setting
• Added periodic movement enabled on plugin startup

Bug Fixes

• Fixed skip if whitelist and no tags
• Fixed filter code and added skip option for manuell note movement
• Fixed typo in settings
• Fixed interaval reset

0.1.4

Features

• Added rules section to settings
• Added TagSuggest
• Implemented note movement based on rules
• Updated README with updated description
• Added custom log classes

0.1.3 (2025-01-03)

Bug Fixes

• Renamed setting for notes folder
• Set default value for notes folder to vault root

Features

• Added inbox folder setting
• Added command to move all files from inbox to notes folder