praxis-kit 0.1.1 → 1.0.2

package/dist/tailwind/index.d.ts

@@ -17,6 +17,17 @@ import { RequireAtLeastOne, Simplify } from "type-fest";
  * utilities, so no additional prop-to-class mapping is required.
  */
 export declare const layoutKeys: readonly ["flex", "inline-flex", "grid", "inline-grid", "block", "inline-block", "inline", "hidden", "contents", "flow-root", "list-item", "table", "inline-table", "table-caption", "table-cell", "table-column", "table-column-group", "table-footer-group", "table-header-group", "table-row-group", "table-row"];
+/**
+ * The concrete union of layout prop names — the pre-resolved form of
+ * `LayoutKey<typeof layoutKeys>`, colocated with the tuple it derives from.
+ *
+ * For code that needs to *name* the layout keys in a type without also importing the runtime
+ * tuple. A framework adapter uses it to collapse the mutually-exclusive `LayoutProps` union back
+ * out of an *extracted* prop type (`ContractProps<typeof Component>`): there a caller wants "the
+ * layout props exist and are optional `true`s", not the ~22-member discriminated union that the
+ * component's own call signature carries — where "only one may be `true`" is a useful error.
+ */
+type LayoutKeyName = (typeof layoutKeys)[number];
 //#endregion
 //#region ../../lib/foundation/src/string-map.d.ts
 /**
@@ -194,4 +205,4 @@ type LayoutProps<T extends readonly string[]> = ExclusiveTrueProp<LayoutKey<T>>
  */
 export declare function createTailwindPipeline<V extends VariantMap = VariantMap>(options: ClassPipelineOptions<V>, diagnostics: Diagnostics): ClassPlugin<LayoutProps<typeof layoutKeys>>;
 //#endregion
-export type { LayoutKey, LayoutProps, ResolvedLayout };
+export type { LayoutKey, LayoutKeyName, LayoutProps, ResolvedLayout };