@bluepic/embed 0.4.0-next.197 → 0.4.0-next.199

package/dist/components/fields/Image.vue.d.ts

@@ -1,4 +1,4 @@
-import { BluepicField, FieldsBridge, ImageLibrary, ImageMime } from '@bluepic/types';
+import { BluepicField, FieldsBridge, ImageLibrary, ImageMime, Template } from '@bluepic/types';
 type __VLS_Props = {
     layout: 'compact' | 'normal';
     allowUploadFromDevice: boolean;
@@ -16,12 +16,27 @@ type __VLS_Props = {
     field?: BluepicField;
 };
 type __VLS_PublicProps = __VLS_Props & {
-    'modelValue': string;
+    /**
+     * The bound value.
+     *
+     * Typed as `ImageValue | string` because BOTH shapes occur in the wild: a
+     * template whose image element is bound straight to a src holds a plain string,
+     * while one where the element's image value carries settings of its own (crop,
+     * mirror flags, `removeBackground`) holds the whole object — `setPropertyValue`
+     * in bx-studio writes the object INTO the binding whenever the element's
+     * property expression is a simple binding key.
+     *
+     * Reading is via `imageSource`; writing MUST go through `handleImageSelection`,
+     * which preserves the object. Assigning a bare string here would silently drop
+     * every other key on the value — that is exactly how background removal was
+     * lost on the first upload.
+     */
+    'modelValue': Template.ImageValue | string;
 };
 declare const _default: import("vue").DefineComponent<__VLS_PublicProps, {}, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {
-    "update:modelValue": (value: string) => any;
+    "update:modelValue": (value: string | Template.ImageValue) => any;
 }, string, import("vue").PublicProps, Readonly<__VLS_PublicProps> & Readonly<{
-    "onUpdate:modelValue"?: ((value: string) => any) | undefined;
+    "onUpdate:modelValue"?: ((value: string | Template.ImageValue) => any) | undefined;
 }>, {
     maxSize: number;
     uploadLabel: string;