mdrefine 0.2.4 → 0.2.5

package/docs/rules.md

@@ -290,7 +290,8 @@ only when the new destination leads to the same file and fragment.
 - `extension`: whether the path to a Markdown file ends in `.md`. `omit` applies
   in the Obsidian dialect only.
 - `leadingDot`: with `relative`, start a path with `./` when it does not start
-  with `.`.
+  with `./` or `../`, also a path to a name that starts with a dot, such as
+  `./.gitignore`.
 
 A relative path also gets `./` when it would otherwise name a different file at
 the vault's root. A destination that already has the configured spelling keeps
@@ -447,7 +448,9 @@ Options: none.
 
 Writes the type of an Obsidian callout in lowercase, custom types included. The
 title and the body are left as written, and so is a marker written with an
-escape or a character reference, such as `\[!TIP]`.
+escape or a character reference, such as `\[!TIP]`, and one that Obsidian shows
+as text because more than one space or a tab separates it from the quote's `>`,
+as in `>  [!TIP]`.
 
 Before:
 
@@ -611,7 +614,9 @@ lines at the start and at the end of a document. The option `maximum` is an
 integer of at least 1; the default is 1. The line break that ends the last line
 stays; [`style/final-newline`](#stylefinal-newline) adds it where it is missing.
 Inside a block quote, a line of only `>` markers is a blank line, and repeated
-ones are removed the same way.
+ones are removed the same way. In the Obsidian dialect, a line of blank space
+that holds a tab, or that lies directly below an HTML block, is not blank:
+Obsidian's Reading view reads it as more of the paragraph or block above it.
 
 Before, with three blank lines between the blocks and two at the end:
 
@@ -783,6 +788,12 @@ so are the exceptions of [Forgejo and Gitea](dialects.md#forgejo-and-gitea):
   `x~~_b_~~`, which GitHub reads as inside a word.
 - Text whose markers CommonMark pairs otherwise than the parser, as in
   `xab***a* a*y`: GitHub follows CommonMark, so the parser misread the text.
+- In Obsidian, a paragraph, heading, or table cell whose text holds a `*` or `_`
+  that is not a marker, as in `snake_case` or `5 * 3`. Obsidian's Reading view
+  pairs such a character with a later one, so `snake_case and _em_` shows
+  `case and _em` as emphasis, and `snake_case and *em*` is right only with the
+  `*` kept. Escaped characters and those in code, math, or wikilinks do not
+  count.
 
 ## `style/final-newline`
 
@@ -1179,14 +1190,16 @@ Line one\
 line two
 ```
 
-Blank space is left as written where it is content: in code blocks, except on
-their fence lines, and in HTML, math, front matter, Obsidian comments, code
-spans, and link titles and labels that span lines. With `"backslash"`, a break
-stays as spaces where a backslash would change what the line says: after another
-backslash, after a literal autolink such as `www.example.com`, which would take
-the backslash into its address, on the title line of an alert or callout, in a
-paragraph that starts like a link reference definition (`[label]:`), and on
-Forgejo and Gitea inside `\(...\)` math.
+Blank space is left as written where it is content: on a line of blank space
+that holds a tab or lies directly below an HTML block in the Obsidian dialect,
+which Obsidian's Reading view reads as more of the block above it; in code
+blocks, except on their fence lines, and in HTML, math, front matter, Obsidian
+comments, code spans, and link titles and labels that span lines. With
+`"backslash"`, a break stays as spaces where a backslash would change what the
+line says: after another backslash, after a literal autolink such as
+`www.example.com`, which would take the backslash into its address, on the title
+line of an alert or callout, in a paragraph that starts like a link reference
+definition (`[label]:`), and on Forgejo and Gitea inside `\(...\)` math.
 
 ## `style/wrap`
 
@@ -1204,9 +1217,10 @@ onto one, without the spaces and tabs that start its next line, as renderers
 read it. On a lazy continuation line, which keeps them, such a code span stays
 as written, and so does its paragraph. In Obsidian, the text of a link stays
 whole and is joined onto one line too, because Live Preview shows a link whose
-text spans lines as its Markdown source. List markers, block quote markers, and
-indentation count toward the width, a tab up to the next multiple of four
-columns.
+text spans lines as its Markdown source. For the same reason, an inline footnote
+(`^[…]`) on one line stays whole there, and a paragraph with one that spans
+lines keeps its lines. List markers, block quote markers, and indentation count
+toward the width, a tab up to the next multiple of four columns.
 
 A word that would start a block at the start of a line, such as a list marker,
 `#`, `>`, a run of `-` or `=`, or a table delimiter row such as `|---|`, stays

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mdrefine",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Configurable Markdown linting and formatting for CommonMark, GitHub, Forgejo, Gitea, and Obsidian",
   "keywords": [
     "markdown",
@@ -91,6 +91,8 @@
     "docs:preview": "vitepress preview docs",
     "benchmark": "node benchmarks/run.mjs",
     "prebenchmark": "npm run build",
+    "check:obsidian": "run-s build check:obsidian:run",
+    "check:obsidian:run": "node scripts/obsidian-check.mjs",
     "release:prepare": "run-s check release:pack",
     "release:pack": "node scripts/package-smoke.mjs --retain",
     "schema": "run-s build schema:write",