@wtfalch/design 0.10.0 → 0.10.1

package/dist/components/Input.d.ts

@@ -19,6 +19,16 @@ export interface Props extends Omit<React.InputHTMLAttributes<HTMLInputElement>,
      *  opens this, which is what the mail client's `.mail-search-key` was. */
     trailing?: React.ReactNode;
     className?: string;
+    /** Accepted and not rendered. `Field`'s render prop hands a caller every
+     *  piece of its wiring at once, and the documented way to use it is
+     *  `<Field>{(f) => <Input {...f} />}</Field>` -- so `labelId` arrives here
+     *  whether or not this control wants it. `Select` does want it, because a
+     *  button takes its name from its contents; an `<input>` does not, because
+     *  `Field`'s `<label for>` already names it. Taking it out of the props is
+     *  what keeps it off the DOM node: React passes through anything it does
+     *  not recognise, and the browser got `labelid="…"` with a console warning
+     *  on every field in valet and tf. */
+    labelId?: string;
 }
 declare const Input: import("react").ForwardRefExoticComponent<Props & import("react").RefAttributes<HTMLInputElement>>;
 export default Input;

package/dist/components/Input.js

@@ -49,7 +49,7 @@ import { forwardRef, useState } from 'react';
 import { ToggleButton } from 'react-aria-components';
 import Icon from './Icon.js';
 import { useFieldWiring } from './fieldWiring.js';
-const Input = forwardRef(function Input({ size = 'md', mono, block, className, type = 'text', icon, onClear, trailing, ...rest }, ref) {
+const Input = forwardRef(function Input({ size = 'md', mono, block, className, type = 'text', icon, onClear, trailing, labelId: _labelId, ...rest }, ref) {
     /* What the `Field` above wired, when the caller did not thread it by hand.
        Explicit props win: a caller that named an `id` meant that id, and a
        render-prop `Field` spreading its wiring is passing the same values in

package/dist/components/Textarea.d.ts

@@ -4,6 +4,16 @@ export interface Props extends Omit<React.TextareaHTMLAttributes<HTMLTextAreaEle
      *  characters are the content. */
     mono?: boolean;
     className?: string;
+    /** Accepted and not rendered. `Field`'s render prop hands a caller every
+     *  piece of its wiring at once, and the documented way to use it is
+     *  `<Field>{(f) => <Input {...f} />}</Field>` -- so `labelId` arrives here
+     *  whether or not this control wants it. `Select` does want it, because a
+     *  button takes its name from its contents; an `<input>` does not, because
+     *  `Field`'s `<label for>` already names it. Taking it out of the props is
+     *  what keeps it off the DOM node: React passes through anything it does
+     *  not recognise, and the browser got `labelid="…"` with a console warning
+     *  on every field in valet and tf. */
+    labelId?: string;
 }
 declare const Textarea: import("react").ForwardRefExoticComponent<Props & import("react").RefAttributes<HTMLTextAreaElement>>;
 export default Textarea;

package/dist/components/Textarea.js

@@ -15,7 +15,7 @@ import { jsx as _jsx } from "react/jsx-runtime";
  */
 import { forwardRef } from 'react';
 import { useFieldWiring } from './fieldWiring.js';
-const Textarea = forwardRef(function Textarea({ size = 'md', mono, className, ...rest }, ref) {
+const Textarea = forwardRef(function Textarea({ size = 'md', mono, className, labelId: _labelId, ...rest }, ref) {
     const classes = [size === 'md' ? '' : `size-${size}`, mono ? 'mono' : '', className ?? '']
         .filter(Boolean)
         .join(' ');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wtfalch/design",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "description": "wtfalch's design system: themeable components on a fixed token vocabulary.",
   "keywords": [
     "design-system",