small improvements

Author: mProjectsCode

bun.lockb

@@ -1,27 +1,27 @@
 {
-	"name": "",
-	"type": "module",
-	"version": "0.0.1",
-	"scripts": {
-		"dev": "astro dev",
-		"start": "astro dev",
-		"build": "astro build",
-		"preview": "astro preview",
-		"astro": "astro",
-		"format": "prettier --plugin prettier-plugin-astro --plugin prettier-plugin-svelte --write ."
-	},
-	"dependencies": {
-		"@astrojs/starlight": "^0.22.3",
-		"astro": "^4.8.3",
-		"starlight-links-validator": "^0.8.0",
-		"starlight-typedoc": "^0.12.1",
-		"typedoc": "^0.25.13",
-		"typedoc-plugin-markdown": "4.0.0-next.60",
-		"typedoc-plugin-mdn-links": "^3.1.25"
-	},
-	"devDependencies": {
-		"prettier": "^3.2.5",
-		"prettier-plugin-astro": "^0.13.0",
-		"prettier-plugin-svelte": "^3.2.3"
-	}
+  "name": "",
+  "type": "module",
+  "version": "0.0.1",
+  "scripts": {
+    "dev": "astro dev",
+    "start": "astro dev",
+    "build": "astro build",
+    "preview": "astro preview",
+    "astro": "astro",
+    "format": "prettier --plugin prettier-plugin-astro --plugin prettier-plugin-svelte --write ."
+  },
+  "dependencies": {
+    "@astrojs/starlight": "^0.23.2",
+    "astro": "^4.8.3",
+    "starlight-links-validator": "^0.8.0",
+    "starlight-typedoc": "^0.12.1",
+    "typedoc": "^0.25.13",
+    "typedoc-plugin-markdown": "4.0.0-next.60",
+    "typedoc-plugin-mdn-links": "^3.1.25"
+  },
+  "devDependencies": {
+    "prettier": "^3.2.5",
+    "prettier-plugin-astro": "^0.13.0",
+    "prettier-plugin-svelte": "^3.2.3"
+  }
 }

package.json

@@ -3,12 +3,12 @@ title: Advanced Use-Cases
 description: A collection of more advanced use-cases.
 ---
 
-If you are willing to dip your toes into the world of JavaScript, you can do quite a few interesting things with Meta Bind.
+If you are willing to dip your toes into the world of [JavaScript](https://developer.mozilla.org/en-US/docs/Learn/JavaScript), you can do quite a few interesting things with Meta Bind.
 
 :::note
 The following examples assume that you have:
 1. [JS Engine](https://github.com/mProjectsCode/obsidian-js-engine-plugin) installed and enabled.
-2. Enabled **JS Input Fields** in the Meta Bind settings.
+2. Enabled **JavaScript** in the Meta Bind settings.
 :::
 
 :::caution

src/content/docs/guides/advancedUseCases.mdx

@@ -21,7 +21,7 @@ Bind Targets consist of three parts.
 storageType^storagePath#property
 ```
 
-Certain parts can be omitted, causing them to default to their default values.
+The `storageType` and `storagePath` can be omitted, causing them to default to their default values.
 
 The following bind target will always use the default storage type `frontmatter`,
 meaning it points to a frontmatter property.
@@ -30,14 +30,17 @@ meaning it points to a frontmatter property.
 storagePath#property
 ```
 
-The following bind targets will always use the current file as the storage path.
+The following bind targets will always use the containing file as the storage path.
+Containing file means the file the bind target or field, that the bind target is part of, is in.
 
 ```meta-bind
 property
 
 storageType^property
 ```
 
+### Default Values Example
+
 This means that the following bind targets are **equivalent**, assuming the current file is `Test Note`.
 
 ```meta-bind
@@ -76,7 +79,8 @@ Global Memory is shared between all notes and **will be lost** when you restart
 ### 2. The Storage Path
 
 The storage path usually points to a file.
-If omitted, it defaults to the current file.
+If omitted, it defaults to the containing file.
+Containing file means the file the bind target or field, that the bind target is part of, is in.
 
 #### Example
 

src/content/docs/guides/bindTargets.md

@@ -5,22 +5,14 @@ description: A tutorial for setting up Meta Bind to work in publish.
 
 :::danger
 
-The publish version of Meta Bind is quite a burden for me to maintain, so it has been falling behind the main version.
-The current publish version probably **won't work**.
+I am currently waiting for the Obsidian Team to deliver on promised improvements to the Obsidian Publish API.
+Until then, Meta Binds publish support will be broken.
 
-Use at your own risk until I can find the time to fix it.
+Use at your own risk. I do not accept issues and feature requests for publish specific issues at this point in time.
 
 :::
 
 This guide assumes that you already have Obsidian Publish set up with a custom domain, so that you can use a `publish.js` file.
 
 To get meta bind working in Obsidian Publish, you need to copy the contents of [this file](https://github.com/mProjectsCode/obsidian-meta-bind-plugin/blob/master/PublishLoad.js) into your `publish.js` file.
-For the correct appearance, you need to copy [this file](https://github.com/mProjectsCode/obsidian-meta-bind-plugin/blob/master/styles.css) into your `publish.css` file.
-
-## What it can do and what it can't
-
-For input fields, due to the limited publish API, the plugin will only display the bound metadata instead of showing input field.
-
-View fields should be mostly functional.
-
-Binding to metadata of a different note is not possible for both fields.
+For the correct appearance, you need to copy [this file](https://github.com/mProjectsCode/obsidian-meta-bind-plugin/blob/master/styles.css) into your `publish.css` file.

src/content/docs/guides/obsidianPublish.md

@@ -142,7 +142,10 @@ Those can only be created as code blocks and **not inline**.
 By default, JS View Fields are disabled, as they can pose a security risk.
 
 :::note
-This requires the [JS Engine](https://github.com/mProjectsCode/obsidian-js-engine-plugin) plugin to be installed and enabled.
+This feature requires the that you have the following:
+
+1. [JS Engine](https://github.com/mProjectsCode/obsidian-js-engine-plugin) installed and enabled.
+2. Enabled **JavaScript** in the Meta Bind settings.
 :::
 
 JS View Fields consist of two sections, separated by `---`.

src/content/docs/guides/viewFields.mdx

@@ -6,7 +6,10 @@ description: Inline JS button action reference.
 The inline JS action runs the code provided using the JS Engine plugin.
 
 :::note
-This requires the [JS Engine](https://github.com/mProjectsCode/obsidian-js-engine-plugin) plugin to be installed and enabled.
+This feature requires the that you have the following:
+
+1. [JS Engine](https://github.com/mProjectsCode/obsidian-js-engine-plugin) installed and enabled.
+2. Enabled **JavaScript** in the Meta Bind settings.
 :::
 
 ```ts

src/content/docs/reference/buttonActions/inlineJs.mdx

@@ -6,7 +6,10 @@ description: Run JavaScript File button action reference.
 The run JavaScript file action runs a JavaScript file.
 
 :::note
-This requires the [JS Engine](https://github.com/mProjectsCode/obsidian-js-engine-plugin) plugin to be installed and enabled.
+This feature requires the that you have the following:
+
+1. [JS Engine](https://github.com/mProjectsCode/obsidian-js-engine-plugin) installed and enabled.
+2. Enabled **JavaScript** in the Meta Bind settings.
 :::
 
 ```ts

src/content/docs/reference/buttonActions/runJavaScript.mdx

@@ -18,6 +18,13 @@ interface UpdateMetadataButtonAction {
 If `evaluate` is set to `true`, the value is treated as a JavaScript expression and evaluated.
 The current value of the property is available in the expression as `x`.
 
+:::note
+The evaluate feature requires that you have the following:
+
+1. [JS Engine](https://github.com/mProjectsCode/obsidian-js-engine-plugin) installed and enabled.
+2. Enabled **JavaScript** in the Meta Bind settings.
+:::
+
 #### Example
 
 This button group allows you to increment, decrement, and reset a counter stored in the frontmatter of the current file.