@allxsmith/bestax-bulma 5.15.3 → 5.15.4

package/dist/types/helpers/anchorAttrs.d.ts

@@ -0,0 +1,37 @@
+import type React from 'react';
+/**
+ * Exactly what `<a>` adds over the attributes every element has: `href`,
+ * `target`, `download`, `hrefLang`, `ping`, `referrerPolicy`, `media`, `type`.
+ *
+ * Subtracted from React's own types rather than listed. Listing them is how
+ * `Level.Item` came to reject `download` at `as="a"` — its list said `href`,
+ * `target`, `rel` and stopped (#641). A list gains an entry when someone
+ * notices; a subtraction gains it when React does.
+ *
+ * NOT `rel`: React declares it on `HTMLAttributes`, for every element, so the
+ * subtraction removes it. A component that withholds `rel` from a non-anchor is
+ * making a compatibility choice rather than stating a fact about anchors, and
+ * says so where it makes it.
+ */
+export type AnchorOnlyAttributes = Omit<React.AnchorHTMLAttributes<HTMLAnchorElement>, keyof React.HTMLAttributes<HTMLAnchorElement>>;
+/**
+ * The runtime mirror of `AnchorOnlyAttributes`, keyed so the two cannot drift.
+ *
+ * `Record<keyof …, true>` is what links them: the day React adds an anchor
+ * attribute, every component deriving its props from `as` accepts it and this
+ * object stops compiling until it is named here. A plain array beside a derived
+ * type drifts in the one direction that matters — the type accepts the new
+ * attribute and the filter lets it leak onto a `<div>`.
+ */
+export declare const ANCHOR_ONLY_ATTRS: Readonly<Record<keyof AnchorOnlyAttributes, true>>;
+/**
+ * `props` without the keys named in `strip`.
+ *
+ * The SET is per component and deliberately not shared, because the right
+ * answer differs and the differences are principled: how open the component's
+ * `as` is, and which of these attributes its own tags legitimately take. What
+ * IS shared is the derived source of truth above and this function. Each caller
+ * declares its delta next to the set it passes, which is the only place that
+ * stays true when a component's `as` changes.
+ */
+export declare function omitAttrs<T extends object, K extends string>(props: T, strip: Readonly<Record<K, true>>): Omit<T, K>;

package/dist/types/layout/Level.d.ts

@@ -1,4 +1,5 @@
 import React from 'react';
+import { type AnchorOnlyAttributes } from '../helpers/anchorAttrs';
 import { BulmaClassesProps, validColors } from '../helpers/useBulmaClasses';
 /**
  * Props for the Level component.
@@ -64,38 +65,20 @@ export interface LevelRightProps extends React.HTMLAttributes<HTMLDivElement>, O
  * @returns {JSX.Element} The rendered level right section.
  */
 export declare const LevelRight: React.FC<LevelRightProps>;
-/**
- * Exactly what `<a>` adds over the attributes every element has: `href`,
- * `target`, `download`, `hrefLang`, `ping`, `referrerPolicy`, `media`, `type`.
- *
- * NOT `rel`, which React declares on `HTMLAttributes` for every element and the
- * subtraction therefore removes. This component withholds it from a non-anchor
- * anyway, because it always has — see `ANCHOR_ONLY` in the implementation,
- * where it is named separately for that reason.
- *
- * Subtracted from React's own types rather than listed. Listing them is how this
- * component came to reject `download` at `as="a"` — the list said `href`,
- * `target`, `rel` and stopped, and #641 is the report. A list gains an entry only
- * when someone notices; a subtraction gains it when React does.
- *
- * They reach the `<a>` branch and no other: declared at every `as` because
- * narrowing them to the anchor is source-breaking (#672, `next-major`), and
- * withheld at runtime so the type's permissiveness costs no dead markup.
- */
-type AnchorOnlyAttributes = Omit<React.AnchorHTMLAttributes<HTMLAnchorElement>, keyof React.HTMLAttributes<HTMLAnchorElement>>;
 /**
  * Props for the LevelItem component.
  *
- * The anchor attributes are enumerated here, at every `as`, and forwarded only
- * when the tag is an `<a>` — so `<Level.Item as="p" download>` compiles and
+ * The anchor attributes arrive through `AnchorOnlyAttributes`, at every `as`, and
+ * are forwarded only when the tag is an `<a>` — so `<Level.Item as="p" download>` compiles and
  * renders a `<p>` without it. That asymmetry is deliberate for now: deriving
  * them from `as` instead is what makes the dead pair a type error, and it also
  * stops `const p: LevelItemProps = { href }` compiling for consumers who write
  * it today. #672 carries that half, labelled `next-major`.
  *
- * What this list must NOT become is a shorter one. Enumerating only `href`,
+ * What that set must NOT become is a hand-written list. Enumerating only `href`,
  * `target` and `rel` made every other anchor attribute a type error even at
- * `as="a"`, which is what #641 reported.
+ * `as="a"`, which is what #641 reported; `helpers/anchorAttrs.ts` derives it from
+ * React instead, and `ANCHOR_ONLY_ATTRS` there is the guard to protect.
  */
 export interface LevelItemProps extends AnchorOnlyAttributes, React.HTMLAttributes<HTMLDivElement | HTMLParagraphElement | HTMLAnchorElement>, Omit<BulmaClassesProps, 'color' | 'backgroundColor'> {
     /** Element type to render. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@allxsmith/bestax-bulma",
-  "version": "5.15.3",
+  "version": "5.15.4",
   "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",