@allxsmith/bestax-bulma 5.8.4 → 5.9.1

package/dist/types/elements/LinkButton.d.ts

@@ -4,7 +4,7 @@ import { ButtonProps } from './Button';
  * Props for the LinkButton component.
  */
 export interface LinkButtonProps extends Omit<ButtonProps, 'color' | 'isOutlined' | 'isInverted' | 'isLight'> {
-    /** Display mode. `text` has no underline; `ghost` uses default text color. */
+    /** Display mode. `text` has no underline and highlights its background on hover; `ghost` uses the default text color and underlines on hover; `underline` drops the button chrome entirely (transparent background and border) and underlines on hover or focus. */
     variant?: 'text' | 'ghost' | 'underline';
     /** Text color override for the button. */
     color?: 'primary' | 'link' | 'info' | 'success' | 'warning' | 'danger' | 'white' | 'light' | 'dark' | 'black';

package/dist/types/form/Field.d.ts

@@ -12,11 +12,11 @@ export interface FieldProps extends React.HTMLAttributes<HTMLDivElement>, Omit<B
     hasAddons?: boolean | 'centered' | 'right';
     /** Constrains the field to its content's width (used inside horizontal field bodies). */
     narrow?: boolean;
-    /** Field label, rendered above the widget. `Field` itself does not associate it with any control — pass `labelProps={{ htmlFor }}` and a matching `id` on your control (the single-control convenience inputs do this automatically when they render their own `Field`). */
+    /** Field label, rendered above the widget. Automatically associated with a single composed `InputBase`, `SelectBase`, or `TextAreaBase` via a generated id and `htmlFor`. Pass `labelProps={{ htmlFor }}` to wire your own `id`, or `labelProps={{ htmlFor: undefined }}` to opt out. Skipped for `grouped`/`hasAddons` fields (multiple controls). */
     label?: React.ReactNode;
     /** Size for the label. */
     labelSize?: 'small' | 'normal' | 'medium' | 'large';
-    /** Props for the label element — where `htmlFor` goes when composing. */
+    /** Props for the label element. An explicit `htmlFor` key — even set to `undefined` — takes over the association. */
     labelProps?: React.LabelHTMLAttributes<HTMLLabelElement> & {
         [key: string]: unknown;
     };

package/dist/types/form/FormContext.d.ts

@@ -12,6 +12,16 @@ export declare const useInsideControl: () => boolean;
 export declare const FieldProvider: import("react").Provider<boolean>;
 /** Provider for Control context — used internally by Control component. */
 export declare const ControlProvider: import("react").Provider<boolean>;
+/**
+ * The id a labeled Field wants its single composed control to adopt (#495).
+ * `undefined` outside a Field, in unlabeled/grouped/addons Fields, or when the
+ * user took over the association with an explicit `labelProps.htmlFor`.
+ * Consumed only by the single-control bases (InputBase, SelectBase,
+ * TextAreaBase). Internal; not part of the public API.
+ */
+export declare const useFieldLabelId: () => string | undefined;
+/** Provider for the Field label-target id — used internally by Field. */
+export declare const FieldLabelIdProvider: import("react").Provider<string | undefined>;
 /**
  * Shape of the Radios group context. The group provides:
  * - `name`: shared form field name (Stage 1)

package/dist/types/form/Input.d.ts

@@ -10,11 +10,11 @@ import { InputBaseProps } from './InputBase';
  * Control-level (icons, loading) props.
  */
 export interface InputProps extends InputBaseProps {
-    /** Field label. Automatically associated with the input via `htmlFor` — uses your `id` when provided, otherwise a generated one. Dropped inside an outer `Field` (label that `Field` yourself). */
+    /** Field label. Automatically associated with the input via `htmlFor` — uses your `id` when provided, otherwise a generated one. Dropped inside an outer `Field`, whose own label associates instead when that `Field` generates a target id (not `grouped`/`hasAddons`, no explicit `labelProps.htmlFor`). */
     label?: React.ReactNode;
     /** Size for the label. */
     labelSize?: FieldProps['labelSize'];
-    /** Props for the label element. An explicit `htmlFor` here overrides the automatic association (no id is generated then). */
+    /** Props for the label element when the component renders its own `Field`; dropped inside an outer `Field` (use that `Field`'s `labelProps` instead). An explicit `htmlFor` key — even `undefined` — overrides the automatic association and no id is generated. */
     labelProps?: FieldProps['labelProps'];
     /** Horizontal field layout. */
     horizontal?: boolean;

package/dist/types/form/Select.d.ts

@@ -10,11 +10,11 @@ import { SelectBaseProps } from './SelectBase';
  * Control-level (icons, loading) props.
  */
 export interface SelectProps extends SelectBaseProps {
-    /** Field label. Automatically associated with the select via `htmlFor` — uses your `id` when provided, otherwise a generated one. Dropped inside an outer `Field` (label that `Field` yourself). */
+    /** Field label. Automatically associated with the select via `htmlFor` — uses your `id` when provided, otherwise a generated one. Dropped inside an outer `Field`, whose own label associates instead when that `Field` generates a target id (not `grouped`/`hasAddons`, no explicit `labelProps.htmlFor`). */
     label?: React.ReactNode;
     /** Size for the label. */
     labelSize?: FieldProps['labelSize'];
-    /** Props for the label element. An explicit `htmlFor` here overrides the automatic association (no id is generated then). */
+    /** Props for the label element when the component renders its own `Field`; dropped inside an outer `Field` (use that `Field`'s `labelProps` instead). An explicit `htmlFor` key — even `undefined` — overrides the automatic association and no id is generated. */
     labelProps?: FieldProps['labelProps'];
     /** Horizontal field layout. */
     horizontal?: boolean;

package/dist/types/form/TextArea.d.ts

@@ -10,11 +10,11 @@ import { TextAreaBaseProps } from './TextAreaBase';
  * Control-level (loading) props.
  */
 export interface TextAreaProps extends TextAreaBaseProps {
-    /** Field label. Automatically associated with the textarea via `htmlFor` — uses your `id` when provided, otherwise a generated one. Dropped inside an outer `Field` (label that `Field` yourself). */
+    /** Field label. Automatically associated with the textarea via `htmlFor` — uses your `id` when provided, otherwise a generated one. Dropped inside an outer `Field`, whose own label associates instead when that `Field` generates a target id (not `grouped`/`hasAddons`, no explicit `labelProps.htmlFor`). */
     label?: React.ReactNode;
     /** Size for the label. */
     labelSize?: FieldProps['labelSize'];
-    /** Props for the label element. An explicit `htmlFor` here overrides the automatic association (no id is generated then). */
+    /** Props for the label element when the component renders its own `Field`; dropped inside an outer `Field` (use that `Field`'s `labelProps` instead). An explicit `htmlFor` key — even `undefined` — overrides the automatic association and no id is generated. */
     labelProps?: FieldProps['labelProps'];
     /** Horizontal field layout. */
     horizontal?: boolean;

package/dist/types/form/useAutoLabelId.d.ts

@@ -18,8 +18,9 @@ interface UseAutoLabelIdOptions {
  * Associates the convenience `label` prop with its control (#368): generates
  * an id for the control and returns labelProps carrying a matching `htmlFor`.
  * A user-supplied `id` is used as the target instead of the generated one, and
- * an explicit `labelProps.htmlFor` disables generation entirely — the user has
- * taken over the association. Internal; not part of the public API.
+ * an explicit `htmlFor` key in labelProps — even set to `undefined` — disables
+ * generation entirely: the user has taken over the association (#495 presence
+ * semantics). Internal; not part of the public API.
  */
 export declare function useAutoLabelId({ label, id, labelProps, rendersLabel, }: UseAutoLabelIdOptions): {
     controlId: string | undefined;

package/llms.txt

@@ -7,3 +7,4 @@ React components for Bulma v1.
 - Any docs page as markdown: append .md (e.g. https://bestax.io/docs/api/elements/button.md)
 - LLM guide: https://bestax.io/docs/guides/llms
 - Agent skills: https://bestax.io/docs/skills/intro
+- MCP server: `npx bestax-mcp` — setup at https://bestax.io/docs/guides/llms#mcp-server

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@allxsmith/bestax-bulma",
-  "version": "5.8.4",
+  "version": "5.9.1",
   "description": "A fully-typed React component library for the Bulma CSS framework. Build modern UIs quickly with reusable, accessible, and customizable Bulma-based React components.",
   "main": "dist/index.cjs.js",
   "module": "dist/index.esm.js",