@tiptap/core 3.20.2 → 3.20.3

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@tiptap/core",
   "description": "headless rich text editor",
-  "version": "3.20.2",
+  "version": "3.20.3",
   "homepage": "https://tiptap.dev",
   "keywords": [
     "tiptap",
@@ -52,10 +52,10 @@
     "jsx-dev-runtime"
   ],
   "devDependencies": {
-    "@tiptap/pm": "^3.20.2"
+    "@tiptap/pm": "^3.20.3"
   },
   "peerDependencies": {
-    "@tiptap/pm": "^3.20.2"
+    "@tiptap/pm": "^3.20.3"
   },
   "repository": {
     "type": "git",

package/src/Extendable.ts

@@ -291,6 +291,28 @@ export interface ExtendableConfig<
      * Defines if this markdown element should indent it's child elements
      */
     indentsContent?: boolean
+
+    /**
+     * Lets a mark tell the Markdown serializer which inline HTML tags it can
+     * safely use when plain markdown delimiters would become ambiguous.
+     *
+     * This is mainly useful for overlapping marks. For example, bold followed
+     * by bold+italic followed by italic cannot always be written back with only
+     * `*` and `**` in a way that still parses correctly. In that case, the
+     * serializer can close the overlapping section with markdown and reopen the
+     * remaining tail with HTML instead.
+     *
+     * Example:
+     * - desired formatting: `**123` + `*456*` + `789 italic`
+     * - serialized result: `**123*456***<em>789</em>`
+     *
+     * If your extension defines custom mark names, set `htmlReopen` on that
+     * extension so the serializer can reuse its HTML form for overlap cases.
+     */
+    htmlReopen?: {
+      open: string
+      close: string
+    }
   }
 
   /**

package/src/helpers/isNodeEmpty.ts

@@ -25,7 +25,7 @@ export function isNodeEmpty(
       return true
     }
     if (node.isText) {
-      return /^\s*$/m.test(node.text ?? '')
+      return !/\S/.test(node.text ?? '')
     }
   }
 

package/src/types.ts

@@ -959,6 +959,10 @@ export interface MarkdownExtensionSpec {
   parseMarkdown?: (token: MarkdownToken, helpers: MarkdownParseHelpers) => MarkdownParseResult
   renderMarkdown?: (node: any, helpers: MarkdownRendererHelpers, ctx: RenderContext) => string
   isIndenting?: boolean
+  htmlReopen?: {
+    open: string
+    close: string
+  }
   /** Custom tokenizer for marked.js to handle non-standard markdown syntax */
   tokenizer?: MarkdownTokenizer
 }