* Update devDependencies and adapt to eslint-plugin-obsidianmd 0.4.1
* Bump minAppVersion to 1.13.0 and drop deprecated API usage
* Remove dead ESLint config obsoleted by obsidianmd 0.4.1
- page-navigation: timer callback re-ran display() each tick, leaking a
new interval per tick while hide() cleared only the most recent one.
Create the interval once and update the element from the callback.
- nested-settings: shallow Object.assign in loadSettings dropped sibling
defaults for partial stored objects and let a null section break
predicates. Merge each nested object explicitly.
- migration-simple: validate trimmed before testing but the framework
persists the raw value, silently changing stored data. Validate the
raw value and document that validate cannot normalize.
- Bump @types/node, esbuild, jiti, obsidian, typescript (6.0),
and typescript-eslint to latest
- Hold @eslint/js at 9.x: eslint-plugin-obsidianmd peer-pins ^9.30.1
- tsconfig: drop unused baseUrl and switch moduleResolution to bundler
(both deprecated as errors in TS 6.0)
- main.ts: declare settings to refine Plugin.settings (new in 1.13.0)
- settings.ts: add override to display(); centralise the still-supported
imperative re-render behind rerender() with one deprecation suppression
- Keep setWarning() over setDestructive() to avoid raising minAppVersion
from 1.8.7 to 1.13.0
Add actions/attest-build-provenance step to the release workflow so
main.js and styles.css are signed via Sigstore and verifiable with
`gh attestation verify`. Grants the job id-token: write and
attestations: write to support OIDC token minting and recording.
* Use createSpan helper for file path element
* Use createSpan helper for selection conflict warning
* Use createSpan helper for checkbox-type warning
* Use createSpan helper for selection conflict warning (initial render)
* Use createSpan helper for checkbox-type warning (initial render)
* Upgrade eslint-plugin-obsidianmd to 0.3.0
Apply prefer-window-timers fix for popout window compatibility.
* Move "Delete selected" button to select/deselect row
Addresses #48: the warning-red delete button next to the lighter-red
"Update properties" CTA drew the eye toward delete and made update
look inactive. Move delete to the Select all / Deselect all row,
left-justified, with the same styling as the sibling buttons.
* Let selection row span full modal width
The "Delete selected" button was only pushed left within the right
half of the row. Hide the empty .setting-item-info on this row so the
control area spans the modal, letting margin-right: auto put Delete at
the left edge while Select all / Deselect all stay on the right.
* Upgrade eslint-plugin-obsidianmd to 0.2.4
Pick up new rules: prefer-active-doc, prefer-active-window-timers,
no-unsupported-api, prefer-instanceof, editor-drop-paste,
rule-custom-message, plus the bundled no-unsanitized plugin.
Fix new lint errors:
- Use activeDocument/activeWindow instead of document/window in the
modal and settings (popout compatibility).
- Use activeWindow.setTimeout/clearTimeout for the status bar debouncer.
- Bump minAppVersion to 1.8.7. Notice.messageEl (1.8.7) and
FileManager.trashFile (1.6.6) were already in use, so the previous
1.4.10 floor was incorrect.
Config tweaks:
- Scope a local override to turn off the preset's type-aware
obsidianmd rules on package.json: the 0.2.4 preset spreads them
globally and they crash on the JSON parser.
- Keep reportUnusedDisableDirectives and require-await overrides
(the preset still does not set them).
- Switch from the deprecated tseslint.config() to ESLint core's
defineConfig(). Drop the now-redundant globals dep (the preset
sets browser/obsidian globals itself).
* Pin debounce timers to owning window, not activeWindow
activeWindow resolves at call time, so a timer scheduled in one
window could be cleared against a different window (no-op) if the
user moved focus between schedule and cancel. The stale callback
would still fire and clobber a newer pending timer id.
Capture the owning window via the element's `.win` accessor and use
the same reference for both setTimeout and clearTimeout — status
bar in main.ts, selection-property blur debouncer in settings.ts.
* Pin modal DOM to owning document; bump version to 1.0.8
activeDocument follows focus, so modal code that used it to check
active element or create inputs could target the wrong window when
focus moved between pop-outs. Switch to the owning document of the
relevant element (checkbox.ownerDocument, setting.controlEl.ownerDocument).
Bump plugin version to 1.0.8 and record versions["1.0.8"] = "1.8.7".
Keeping the minAppVersion change under version 1.0.7 would have left
the packaged manifest (1.8.7) disagreeing with the community index
(versions.json mapping 1.0.7 → 1.4.10).
* Revert premature version bump to 1.0.8
Roll package/manifest/versions metadata back to 1.0.7; the version
bump belongs in a separate release commit via `npm version patch`,
not in this branch. minAppVersion stays at 1.8.7 because the code
on this branch uses APIs that require it.
* Address Obsidian review lint findings
Replace `any` casts with typed App extensions for the undocumented
`app.setting` and `app.metadataTypeManager` APIs, remove sentence-case
disables by rephrasing the empty-state link and fallback Notice, and
drop `async` from `toggleSelection` (which never awaited).
Tighten local ESLint config to catch similar issues going forward:
enable `reportUnusedDisableDirectives` and re-enable
`@typescript-eslint/require-await` (the obsidianmd preset disables it).
* Fix stale eslint.config.js references in ESLint config
The config referenced eslint.config.js (from before the rename to .mts)
in both allowDefaultProject and globalIgnores — dead entries since that
file doesn't exist. The real eslint.config.mts was neither allowlisted
for projectService nor explicitly ignored, relying on the obsidianmd
preset's files patterns happening to exclude .mts. An upgrade adding
.mts to that pattern would have made lint fail on the config itself.
Explicitly ignore eslint.config.mts (matching the treatment of the
other build config files) and drop the dead allowDefaultProject entry.
* Add metadata cache warning modal for large bulk operations
When a bulk operation modifies more than 75 notes, show a modal
explaining that Obsidian's metadata cache may take several minutes
to re-index. Includes a "Don't show again" toggle persisted via a
new showLargeOperationWarning setting, re-enableable from the
settings tab. Covers bulk update, bulk delete, deselect all, and
remove selection property entry points.
Also simplifies deselectAll and removeSelectionProperty signatures
to take the plugin instance, deriving app and selectionProperty
from it.
* Pass captured selectionProperty through to doRemove
Restore the original data flow where selectionProperty is captured
once at command start and threaded through, rather than re-read
from plugin.settings inside doRemove. The signature simplification
in the prior commit introduced a subtle re-read that could
mismatch if the setting changed between confirmation and execution.
* Remove cache warning from file deletion, lower threshold to 25
File deletion reconciles in the metadata cache much faster than
property edits (entry removal vs YAML re-parse), so the warning
would be misleading. Also lower LARGE_OPERATION_THRESHOLD from 75
to 25.
* Document scale expectations and cache warning in README
* Avoid hardcoding threshold number in README
* Run withProgress actions through a bounded worker pool
Replace the strict sequential for-loop with a worker pool (concurrency
8) so bulk operations like "Deselect all notes" and the bulk edit
modal's update/delete actions run their per-file processFrontMatter or
trashFile calls in parallel. Progress text updates on completion so the
displayed count is monotonic.
Same public signature; callers are unchanged.
* Run delete sequentially to preserve cancel semantics
Parallel delete meant clicking Cancel could still trash up to 7 more
notes before withProgress returned. Metadata writes are cheap enough
that the regression is invisible, but trashFile runs long enough that
a panicked Cancel should stop promptly.
Add an optional concurrency parameter to withProgress (default 8) and
pass 1 at the delete call site. Other callers are unchanged.
* Add delete action to bulk edit dialog
Adds a "Delete selected files" button alongside "Update properties"
in the bulk edit dialog, routing through app.fileManager.trashFile()
so the user's Obsidian trash preference is honored. The heading is
renamed to "Bulk edit selected files" to reflect the expanded scope.
The no-properties-configured branch no longer returns early so the
Delete button remains available when only a selection is present but
no editable properties are configured.
ConfirmModal gains optional confirmText and confirmStyle so the
delete confirmation can show a red "Delete" button rather than the
default CTA "Continue". doDelete() re-reads getCheckedFiles() after
awaiting pendingSaves to avoid confirming on a stale positive count
that resolves to zero.
* Allow duplicates when merging multitext properties
The merge save path deduplicated new values against the existing
list for every array type, but the UI only enforces dedup for tags
and aliases — multitext pills can intentionally repeat (e.g. a
shopping list with "eggs" twice). The save path silently dropped
those duplicates.
Gate the dedup step on the same DEDUP_TYPES set the UI uses, and
append newValues as-is for multitext. The tags/aliases path is
unchanged.
* Treat null list-property values as empty, not non-list
A frontmatter key like "items:" with no value parses as null, which
hit the non-list fallback and marked the file as skipped. That made
merge impossible against bare or explicitly-null list properties.
Group null with undefined in the current-value conversion: merge
starts from an empty list and appends, delete short-circuits since
there is nothing to remove.
Show a warning in settings when the selection property has a
known non-checkbox type (e.g. Text, Number). The warning appears
both on initial display and when the value changes. If the type
cannot be determined, no warning is shown.
* Link "plugin settings" text to open settings tab in empty-state message
When no properties are configured, the modal now shows "plugin settings"
as a clickable link that closes the modal and navigates directly to the
plugin's settings tab.
* Guard undocumented settings API with feature detection
Check that setting.open and setting.openTabById are functions before
calling them. Falls back to a Notice with manual navigation instructions
if the internal API is absent.
* Add focus-visible indicator for links in the modal
* Make file path labels clickable in bulk edit modal
Use a <label> element instead of a <div> for file rows so clicking
the file path text toggles the checkbox, not just clicking the
checkbox itself.
* Restore checkbox focus after toggle save completes
Disabling the checkbox during save causes the browser to remove focus,
so spacebar stops working until the user tabs away and back. Refocus
the checkbox after re-enabling it.
* Guard checkbox refocus to avoid stealing focus from other controls
Only restore focus to the checkbox after save if the user hasn't
tabbed to another control in the meantime. Checks that activeElement
is still document.body (where it lands after disable) before refocusing.
* Fix type dropdown resetting to first option for unknown properties
The "Choose type…" placeholder <option> was disabled, which prevented
setValue("") from selecting it programmatically. When auto-detect
returned null for a novel property name, the browser fell through to
the first enabled option instead of staying on the placeholder.
* Skip type auto-detect for property names not in the vault
metadataTypeManager.getPropertyInfo() returns {widget: "text"} as a
default for unknown names, causing the type dropdown to silently
pre-fill "Text" for novel properties. Guard with a vault property
name check so the dropdown stays on "Choose type…" instead.
* Block selection property from conflicting with configured properties
Prevent setting the selection property to a value already in the
properties edit list. Validation fires on blur and suggestion selection
(not on every keystroke) to avoid false notices while typing through
a conflicting prefix. Also adds a warning in settings when a
pre-existing conflict is detected on disk.
* Stop persisting intermediate keystrokes for selection property
Move from onChange-based saving to commit-on-blur/suggestion-selection.
This prevents intermediate prefixes from being persisted, so reverting
on conflict always restores the original value. The blur handler is
deferred via setTimeout(0) so a suggestion click can cancel it and
avoid a double-commit race. The on-disk conflict warning now updates
inline after a successful save instead of requiring a full re-render.
* Fix initialization crash and async overwrite race
Move initial warning render outside the addSearch callback so
selectionSetting is fully initialized before descEl is accessed.
The inline updateWarning() still handles dynamic updates after saves.
Restore stale-write guard: capture the draft input value before
awaiting the save, only reset the input if it still matches when
the save completes.
AbstractInputSuggest.setValue() sets the input's .value property directly
without firing an input event, so SearchComponent.onChange() never
executes when a suggestion is clicked. Wire up onSuggestionSelected to
explicitly invoke the save logic after a suggestion is selected.
* Add /release-notes project command
Generates user-facing release notes from merged PRs since the last
GitHub release, categorized into New Features, Enhancements, Bug Fixes,
and Other. Output is saved to the Notes inbox as a timestamped markdown
file for manual review before publishing.
* Use tag commit date instead of release publishedAt for PR cutoff
Draft releases can be published well after the tag is created, which
would cause PRs merged in between to be missed. Deriving the cutoff
from the tag's commit date avoids this gap.
* Move release-notes from command to skill format
Skills support frontmatter (invoke: user for manual-only triggering)
and a directory for supporting files. The /release-notes slash command
works the same way.
* Use committer date instead of author date for tag cutoff
Author date (%aI) can be stale if the tagged commit was rebased or
cherry-picked. Committer date (%cI) reflects when the commit was
actually created on the branch.
* Add merge, replace, and delete actions for array properties (#31)
For tags, aliases, and multitext properties, users can now choose an
action when bulk editing: merge (add to existing values), replace
(overwrite all values), or delete (remove specified values). The action
defaults to merge each time the dialog opens.
Merge deduplicates against existing values and within the incoming
batch using case-sensitive comparison. Files with non-array stored
values are skipped to preserve data. Delete on a missing property is
a no-op. Replace shows a confirmation warning before proceeding.
* Normalize scalar string values to array for merge and delete
Frontmatter commonly stores single tags/aliases values as a scalar
string rather than a one-element array. Normalize these to [string]
before applying merge/delete instead of skipping. Only skip truly
incompatible types (numbers, booleans, objects).
* Update README: move Setup before Usage, use friendly type names
Setup is a prerequisite for using the plugin so it belongs first.
Property types now use the same friendly names shown in the settings
UI (e.g. "Date & time" instead of "datetime", "List" instead of
"multitext").
* Clean up README wording
Usage step 1 now references the configured selection property instead
of re-introducing it. Fix typo in Manual Installation callout.
* Show friendly display names in property type dropdown (#29)
Map internal property type strings to user-friendly labels
matching Obsidian Bases (e.g. "datetime" → "Date & time",
"multitext" → "List") and sort alphabetically.
* Show friendly type label in property list description
* Exclude already-configured properties from name suggestions (#28)
The property name autocomplete in settings now filters out properties
that are already in the configured list, preventing duplicate selection.
* Exclude selection property from add-property suggestions
The selection property is already filtered out of the bulk-edit modal,
so allowing it to be added to the properties list is a confusing no-op.
Exclude it from autocomplete suggestions and reject it in the add-button
validation with a clear message.
* Fix release workflow tag filter and serialize all settings saves
The release workflow tag filter used regex syntax ([0-9]+) but GitHub
Actions expects glob patterns, so it would never match semver tags.
Replace with *.*.*; the manifest/tag equality check remains as strict
validation.
Move the settings save queue from BulkPropertiesSettingTab into the
plugin so all callers (settings tab, bulk-edit modal) share a single
serialized write path, preventing concurrent saves from overwriting
each other.
* Revert release workflow tag filter change
The original [0-9]+.[0-9]+.[0-9]+ pattern is correct. GitHub Actions
filter patterns support + as "one or more of the preceding character",
unlike standard globs. The review finding was based on the incorrect
assumption that + is literal in this context.
* Use copy-on-write semantics for serialized settings saves
updateSetting() on the plugin builds a candidate snapshot and only
assigns it to this.settings after saveData() succeeds. On failure,
in-memory settings remain unchanged, preventing a later unrelated
save from persisting a value that was reported as failed.
Both the settings tab and bulk-edit modal now use this single method
instead of mutating settings before saving.
* Add autocomplete suggestions for tags/multitext pill inputs
Show a completion dropdown with known vault values when entering
tags, aliases, or multitext property values in the bulk edit modal.
Uses AbstractInputSuggest attached to the pill input element.
Suggestions are collected from frontmatter across all vault files,
filtered to exclude already-added pills, and normalized consistently
with tag input (leading # stripped for matching).
* Fix focusout committing partial text when clicking a suggestion
When the user clicks a suggestion in the dropdown, the pill container's
focusout handler fires before selectSuggestion, which would commit the
partially typed query as an unintended pill. Defer the focusout commit
via requestAnimationFrame so selectSuggestion can set a flag and clear
the input first.
* Scope focusout suppression to mouse-triggered suggestions only
Keyboard selections are captured by the suggest's Scope before
focusout fires, so the didSelect flag is only needed for mouse
clicks. Setting it unconditionally left the flag armed after
keyboard selections, which could discard the next legitimate
blur commit.
* Pre-normalize tag values in suggestion list to strip # prefix
Known values for tags are now normalized (leading # removed) before
being passed to the suggest, so the dropdown never shows # prefixes.
Deduplicates after normalization in case both #foo and foo exist.
* Re-sort tag suggestions after normalization
Stripping # prefixes can break the original alphabetical order
from getPropertyValues(). Re-sort after normalize and dedup.
* Fix suggestion selection not adding pill
The selectSuggestion override replaced the base class implementation
that invokes the onSelect callback, so addPill was never called.
Use a direct callback property (onValueSelected) called from within
selectSuggestion, matching the PropertyNameSuggest pattern.
* Fix keyboard and screen reader accessibility for deselect toggle
The toggle in the bulk edit modal ignored Space key when focused via
Tab because Obsidian's ToggleComponent label element doesn't forward
keyboard events. Add a keydown handler for Space and an aria-label so
screen readers announce the checkbox purpose.
* Remove double tab stop and associate label with checkbox input
Remove tabindex from the outer label element so only the native
checkbox input receives focus. Move aria-label onto the input so
screen readers announce "Deselect when finished" for the checkbox.
The native input handles Space key natively, so the custom keydown
handler is no longer needed.
* Fix toggle focus ring size and inverted screen reader state
The native checkbox is smaller than the visual toggle and its checked
state is inverted from the visual state. Fix by keeping focus on the
outer toggleEl (which already has tabindex=0 and the correct visual
size), hiding the native input from tab order and accessibility tree,
and using role=switch with aria-checked that tracks the actual toggle
value. Space key handler on toggleEl triggers the toggle.
* Extract toggle a11y helper and apply to all toggles
Move the toggle accessibility fix (role=switch, aria-checked,
aria-label, Space key handler, hidden native input) into a shared
makeToggleAccessible helper. Apply to all three toggles: the modal
deselect toggle and both settings tab toggles.
* Fix toggle keyboard behavior: Space on keyup, Enter on keydown
Space now prevents default on keydown (to avoid scrolling) but only
toggles on keyup, matching native checkbox behavior. Enter toggles on
keydown. Both ignore repeated key events via e.repeat check.
* Always prevent default for Space keydown to avoid scroll on hold
Move the repeat guard so Space preventDefault runs unconditionally on
keydown (preventing page scroll even when held), while Enter's repeat
guard remains inline to block repeated toggles.
* Prevent silent discard of invalid pill input during bulk edit
addPill now returns a boolean so callers know whether input was
accepted. Invalid text is preserved in the input field on Enter,
paste, and blur instead of being silently dropped. The Update
button is disabled while uncommitted text remains, and doUpdate
guards against proceeding with stale input.
Fixes review #99.
* Fix duplicate pill on Enter for multitext properties
Clear pillInput.value before calling addPill in keydown, paste,
and focusout handlers. renderPills() moves the input element via
appendChild, which fires a focusout event; if the input still held
text, the focusout handler would call addPill a second time. Now
the input is cleared first and restored only if addPill rejects.
* Replace comma-separated textarea with pill-style input for tags
Use Obsidian's native .multi-select-pill CSS classes for tags,
aliases, and multitext property types. Pills are added via Enter,
comma, or paste and removed via × button or Backspace. Dedup
applies to tags/aliases only; multitext allows duplicates. IME
composition is respected to avoid breaking CJK input.
* Add x icon to pill remove button via setIcon
* Fix paste merging and blur commit behavior for pill input
Paste now merges clipboard text with existing input value at the
cursor position before splitting on commas. The trailing segment
after the last comma stays in the input for further editing.
Blur only commits pending text when focus leaves the pill container
entirely, not when clicking a remove button inside it.
* Move pending-text commit to container focusout
Replace the input-level blur handler with a container-level focusout
listener that commits pending text only when focus leaves the pill
container entirely. This covers the keyboard path where focus moves
from a remove button to outside the container.
* Strip border from pill remove button and reduce pill size
* Add hover and focus-visible styles to pill remove button
* Use span with role=button for pill remove to match Obsidian's DOM
Obsidian's native multi-select pills use a span for the remove
control, not a button element. The button element picks up
Obsidian's base button styling (visible border) that can't be
easily overridden. Switching to a span with role="button" and
tabindex="0" matches the native DOM while preserving keyboard
accessibility via an explicit keydown handler.
* Match native button behavior: activate Space on keyup, not keydown
* Validate tag names against Obsidian's naming rules
Reject tags containing spaces, invalid characters, or only digits.
Strip leading # from user input. Show a Notice with the specific
reason when a tag is rejected. Validation applies only to the tags
property type, not aliases or multitext.
* Show notice when bare # is entered as a tag name
* Restore focus to pill input after adding or removing a pill
* Only refocus pill input from keyboard and paste, not blur commits
* Fix duplicate pill on multitext by clearing input before addPill
renderPills() detaches and reattaches the input element, which can
fire a focusout event mid-operation. The focusout handler would then
see the still-populated input and commit the same value again. For
tags/aliases this was masked by dedup, but multitext allows
duplicates so the double-add was visible. Fix by capturing and
clearing the input value before calling addPill.
- Route bulkSetSelection writes through pendingSaves map and add per-file
cleanup in finally blocks so settled entries don't accumulate
- Add confirmation dialog before "Deselect all files" command, consistent
with the existing confirmation on "Remove selection property"
- Debounce status bar updates triggered by metadata-change and file-delete
events (500ms) to avoid redundant full-vault scans during bulk operations
