@thehammer/template-verification 0.2.22 → 0.2.23

package/dist/components/VerifiedField.vue.d.ts

@@ -119,6 +119,28 @@ type __VLS_Props = {
     field?: string;
     original?: string | number | null;
     format?: (value: unknown) => string;
+    /**
+     * SG-974: text to render, styled as an italic placeholder, in place of the
+     * default-slot fallback when this field has no value. Rendered INSIDE
+     * `.tv-field-value` — the same box the real value would occupy — rather
+     * than left for the host template to draw beside `<VerifiedField>` as its
+     * own separate markup.
+     *
+     * That distinction is the whole point, not a style preference. The mark's
+     * anchor is a zero-size box glued to the trailing edge of whatever
+     * `.tv-field-value` rendered (see the header docblock's "ANCHORING"
+     * section) — when there is no value, that box renders NOTHING and
+     * collapses to zero width, so the anchor lands at the field's own
+     * starting point. A placeholder a host template draws AFTER
+     * `<VerifiedField>` as a sibling (`v-if="!value"`) therefore renders
+     * AFTER that zero-width point too, putting the mark to the LEFT of the
+     * placeholder it is supposed to trail — exactly the reported bug (SG-974).
+     * Accepting the placeholder text here and rendering it as the value
+     * box's own content puts it before the anchor in the same inline flow
+     * the anchor already tracks, so the mark lands to its right in every
+     * state, the same guarantee a real value already gets.
+     */
+    placeholder?: string;
 };
 declare const _default: __VLS_WithSlots<import("vue").DefineComponent<__VLS_Props, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {}, string, import("vue").PublicProps, Readonly<__VLS_Props> & Readonly<{}>, {}, {}, {}, {}, string, import("vue").ComponentProvideOptions, false, {}, any>, {
     default?: ((props: {