@webround/core 0.3.11 → 0.3.13

package/dist/text-react.d.ts

@@ -1,5 +1,5 @@
 import React from 'react';
-import type { WrTextTag } from './kinds.js';
+import { type WrTextTag } from './kinds.js';
 export interface WrTextViewProps extends Omit<React.HTMLAttributes<HTMLElement>, 'id' | 'dangerouslySetInnerHTML' | 'children'> {
     id: string;
     /** The container: `div` (default) or `span`. */
@@ -7,5 +7,5 @@ export interface WrTextViewProps extends Omit<React.HTMLAttributes<HTMLElement>,
     /** The HTML of the text, as it is to be drawn. */
     html: string;
 }
-export declare function WrTextView({ id, tag: Tag, html, style, ...props }: WrTextViewProps): React.JSX.Element;
+export declare function WrTextView({ id, tag, html, style, ...props }: WrTextViewProps): React.JSX.Element;
 //# sourceMappingURL=text-react.d.ts.map

package/dist/text-react.js

@@ -1,5 +1,9 @@
 import { jsx as _jsx } from "react/jsx-runtime";
-export function WrTextView({ id, tag: Tag = 'div', html, style, ...props }) {
+import { wrTagOf } from './kinds.js';
+export function WrTextView({ id, tag, html, style, ...props }) {
+    // The types say `div` or `span`, but a site that builds with a type error can say another (`p`, whose paragraphs would be a `<p>` inside a `<p>`, which a parser splits: the saved page and the one the app draws
+    // would differ). Whatever is said, the element is one of the two: the one `wrTagOf` gives, which is also what the checks believe it is.
+    const Tag = wrTagOf('text', tag);
     return (_jsx(Tag, { ...props, "data-wr-id": id, "data-wr-type": "text", dangerouslySetInnerHTML: { __html: html }, style: { wordBreak: 'break-word', ...style } }));
 }
 //# sourceMappingURL=text-react.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@webround/core",
-    "version": "0.3.11",
+    "version": "0.3.13",
     "type": "module",
     "main": "./dist/index.js",
     "module": "./dist/index.js",