@tiptap/core 3.20.2 → 3.20.4

package/dist/index.d.cts

@@ -788,6 +788,27 @@ interface ExtendableConfig<Options = any, Storage = any, Config extends Extensio
          * 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;
+        };
     };
     /**
      * This function extends the schema of the node.
@@ -1789,6 +1810,10 @@ 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;
 }

package/dist/index.d.ts

@@ -788,6 +788,27 @@ interface ExtendableConfig<Options = any, Storage = any, Config extends Extensio
          * 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;
+        };
     };
     /**
      * This function extends the schema of the node.
@@ -1789,6 +1810,10 @@ 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;
 }

package/dist/index.js

@@ -2172,7 +2172,7 @@ function isNodeEmpty(node, {
       return true;
     }
     if (node.isText) {
-      return /^\s*$/m.test((_a = node.text) != null ? _a : "");
+      return !/\S/.test((_a = node.text) != null ? _a : "");
     }
   }
   if (node.isText) {