Skip to content

Releases: gsarig/obsidian-sentinel

1.2.1

30 Mar 15:03

Choose a tag to compare

This release introduces the following improvements:

1. Exclude frontmatter when leaving a note with changes

A new action "Leaving a note with changes, exclude Frontmatter" has been added. It will trigger if the note contains changes, but will ignore any change to the Frontmatter. Addresses the issue: #11

image

The action "Leaving a note with changes" is still there, both for backwards compatibility and for more flexibility, for anyone who wants to trigger an action even when Frontmatter changes.

2. Set variables along with free text

Allows to set variables along with free text, like for example Last update: {{date}}. Addresses the issue #10
This will only work for the variables {{date}}, {{time}} and {{title}}.
This means that {{increment}} is not included and should keep being used without any other text.

Resolved issues

What's Changed

Full Changelog: 1.2.0...1.2.1

1.2.0

16 Mar 15:03

Choose a tag to compare

This release adds a new option "Skip existing", so that the action creates a property only if it doesn’t already exist. This allows Sentinel to be used for things like file creation dates, which are only need to be triggered once in the lifetime of a note.

image

What's Changed

New Contributors

Full Changelog: 1.1.1...1.2.0

1.1.1

14 Mar 10:13

Choose a tag to compare

What's Changed

  • Fixes a bug where the {{title}} parameter didn't work by @gsarig in #7

Full Changelog: 1.1.0...1.1.1

1.1.0

02 Mar 16:27

Choose a tag to compare

Description

Version 1.1.0 includes the following new features:

  • More sophisticated targeting (closes #1). More specifically, you can target with the following additional parameters:
    • #tag - Prefixing the value with a # (e.g. #tag) will match notes that have the specified tag. For example, #tag-1 would trigger the action on any note that includes the tag "tag-1".
    • Folder/ - Putting / at the end of your value (e.g. folder/), will target notes within the specified folder. You can target nested folders like folder/subfolder/. For example, My Folder/ would target all notes under the "My Folder" folder, and My Folder/Subfolder/ all the notes under the specific subfolder.
    • Note name - Putting plain text (e.g. Note Name) will target a note with the exact title (case-insensitive)
    • Negative targeting - The above conditions can be used for negative targeting, by prefixing them with !. For example, !#tag-1 will trigger on any note EXCEPT for those containing the tag "tag-1". !My Folder/ will trigger on any note EXCEPT for those under the "My Folder" folder. !My Note will trigger on any notes EXCEPT for the note with the title "My Note".
    • Multiple targeting - You can use commas to combine multiple conditions. For example, #tag-1,folder/,Note Name will trigger if the note matches ANY of these conditions (has "tag-1" OR is in "folder" OR has the specified name). On the other hand, !#tag-1,!folder/,!Note Name would trigger only if ALL conditions are true (note doesn't have "tag-1" AND isn't in "folder" AND isn't named "Note Name").
  • Adds a new trigger "Closing a note", which runs every time the user leaves a note (closing #4)

Full Changelog: 1.0.2...1.1.0

1.1.0-beta.4

01 Mar 22:09

Choose a tag to compare

1.1.0-beta.4 Pre-release
Pre-release

Fixes a bug with the leaveChanged action and improves the tag matching logic.

Full Changelog: 1.1.0-beta.3...1.1.0-beta.4

1.1.0-beta.3

22 Feb 23:24

Choose a tag to compare

1.1.0-beta.3 Pre-release
Pre-release

1.1.0-beta.2

22 Feb 21:49

Choose a tag to compare

1.1.0-beta.2 Pre-release
Pre-release

Fixes the bug spotted here.
Full Changelog: 1.1.0-beta.1...1.1.0-beta.2

1.1.0-beta.1

22 Feb 17:01

Choose a tag to compare

1.1.0-beta.1 Pre-release
Pre-release

Description

Version 1.1.0 includes the following new features:

  • More sophisticated targeting (closes #1). More specifically, you can target with the following additional parameters:
    • #tag - Prefixing the value with a # (e.g. #tag) will match notes that have the specified tag. For example, #tag-1 would trigger the action on any note that includes the tag "tag-1".
    • Folder/ - Putting / at the end of your value (e.g. folder/), will target notes within the specified folder. You can target nested folders like folder/subfolder/. For example, My Folder/ would target all notes under the "My Folder" folder, and My Folder/Subfolder all the notes under the specific subfolder.
    • Note name - Putting plain text (e.g. Note Name) will target a note with the exact title (case-insensitive)
    • Negative targeting - The above conditions can be used for negative targeting, by prefixing them with !. For example, !#tag-1 will trigger on any note EXCEPT for those containing the tag "tag-1". !My Folder/ will trigger on any note EXCEPT for those under the "My Folder" folder. !My Note will trigger on any notes EXCEPT for the note with the title "My Note".
    • Multiple targeting - You can use commas to combine multiple conditions. For example, #tag-1,folder/,Note Name will trigger if the note matches ANY of these conditions (has "tag-1" OR is in "folder" OR has the specified name). On the other hand, !#tag-1,!folder/,!Note Name would trigger only if ALL conditions are true (note doesn't have "tag-1" AND isn't in "folder" AND isn't named "Note Name").
  • Adds a new trigger "Closing a note", which runs every time the user leaves a note (closing #4)

How to beta test

You can use BRAT to test beta versions of the plugin:

  1. Install the BRAT plugin.
  2. Check the manifest-beta.json file to see the current beta version. For the current release, it should be 1.1.0-beta.1.
  3. Go to BRAT and add the plugin using the option "Add Beta plugin with frozen version":
    obsidian-sentinel-beta-testing.png
  4. Restart your vault.

Changelog

Full Changelog: 1.0.2...1.1.0-beta.1

1.0.2

16 Feb 16:02

Choose a tag to compare

What's Changed

  • Prevents "Opening a note" action from running on split view in #3 (thanks @FelipeRearden)

Full Changelog: 1.0.1...1.0.2

1.0.2-beta.1

16 Feb 12:34

Choose a tag to compare

1.0.2-beta.1 Pre-release
Pre-release

Addressses issue #2

Full Changelog: 1.0.1...1.0.2-beta.1