@ui-organized/vue 0.0.0-stage → 0.1.0

package/dist/props.d.ts

@@ -0,0 +1,50 @@
+/**
+ * Passing "nothing" in Vue.
+ *
+ * React and Svelte both treat an explicit `undefined` as "I am not setting
+ * this": zag's `mergeProps` keeps the machine's value, and the renderer omits
+ * the attribute. Vue does neither.
+ *
+ * - For an **attribute**, `:aria-labelledby="undefined"` *removes* the attribute
+ *   Ark just computed. The merge is last-wins and not undefined-aware.
+ * - For a **declared prop**, `undefined` triggers that prop's declared default.
+ *   Ark's `Switch.Root` declares `checked` with a default of `false`, so passing
+ *   `undefined` actively unchecks a switch that `defaultChecked` had checked.
+ *
+ * - For a **declared Boolean prop**, an *absent* value is cast to `false`, not
+ *   `undefined` — unless the prop declares a default. This is why every
+ *   `defineModel<boolean>` in this package passes `{ default: undefined }`:
+ *   without it an uncontrolled component silently becomes a controlled-off one.
+ *
+ * All three are silent, and all three only show up in the case where the value
+ * mattered. The only way to leave something alone in Vue is not to pass it, so
+ * components build an object and spread it.
+ *
+ * Note the limit: this helper cannot rescue a Boolean prop that Vue has already
+ * cast to `false`, because by then the information that it was absent is gone.
+ * That has to be fixed at the declaration, and it is a rule rather than a
+ * judgement call: **every boolean this helper forwards declares a default of
+ * `undefined`**. Reasoning case by case about which ones matter does not work —
+ * `disabled: false` is harmless because Ark's default is also false, while
+ * `open: false` means "controlled and closed" and pins a popover shut forever.
+ * The second was shipped in five components until a browser test noticed that
+ * clicking a Vue popover's trigger did nothing at all.
+ *
+ * Note where the cast does and does not happen, because the obvious mental model
+ * is wrong in both directions. It is **our own** declaration that casts: most
+ * Ark parts declare their booleans through `mergeDefaults(..., { disabled: void 0 })`,
+ * so handing one an explicit `undefined` is safe and it stays absent. That does
+ * not make this helper redundant — a prop of ours that was already cast to
+ * `false` arrives as a real `false`, and Ark cannot tell that apart from a
+ * deliberate one.
+ *
+ * And Ark is not uniform about it. `SegmentGroup.Item` declares
+ * `disabled: { type: Boolean }` with no defaults object at all, so an absent
+ * value there *is* cast. Check the compiled part rather than assuming; the
+ * pattern holds often enough to be a trap.
+ *
+ * ```vue
+ * <ArkSwitch.Root v-bind="definedOnly({ checked, name, id })" />
+ * ```
+ */
+export declare function definedOnly<T extends Record<string, unknown>>(props: T): Partial<T>;

package/dist/registry-DyLcm8o3.js

@@ -0,0 +1,10 @@
+import { createIconRegistry as e } from "@ui-organized/core";
+const { registerIconSet: s, getIconSet: t, registeredLibraries: o, registerIcons: i, getIcon: a, registeredNames: g } = e(Symbol.for("@ui-organized/vue.iconRegistry"));
+export {
+  a,
+  g as b,
+  s as c,
+  i as d,
+  t as g,
+  o as r
+};