@mk-kit/mcp 0.51.0 → 0.52.0

package/data/api.json

@@ -1,6 +1,6 @@
 {
  "package": "@mk-kit/ui",
- "version": "0.51.0",
+ "version": "0.52.0",
  "site": "https://mk-kit.dev",
  "entries": [
   {
@@ -445,15 +445,6 @@
       "(src: string): string"
      ]
     },
-    {
-     "name": "mkInjectFieldTouched",
-     "description": "Touched-gate for a control's `invalid` input under Signal Forms.\n\nWhen a control is bound with the `[formField]` directive, Angular writes the\nfield's `invalid()` state straight into the control's `invalid` input — from\nthe first render, before the user has reached the field. mk-kit controls\npass that input through this gate so the invalid visual (and `aria-invalid`)\nonly shows once the field is touched or dirty, matching how `mk-form-field`\nreveals its message and how `submit()` (which marks every field touched)\nsurfaces the remaining problems.\n\nReturns a signal that is always `true` for a control that is not bound with\n`[formField]`, so a standalone `[invalid]=\"true\"` keeps working as before.\nCall it in a field initializer (an injection context):\n\n```ts\nprivate readonly fieldTouched = mkInjectFieldTouched();\nprotected readonly isInvalid = computed(\n  () => (this.invalid() && this.fieldTouched()) || (this.field?.hasError() ?? false),\n);\n```\n\nThe binding is looked up lazily, on first read: the `FormField` directive\nitself injects the element's `NG_VALUE_ACCESSOR` (the control) while it is\ncreated, so resolving it from the control's constructor would be circular.",
-     "file": "projects/mk-kit/core/forms/signal-field.ts",
-     "kind": "function",
-     "signatures": [
-      "(): Signal<boolean>"
-     ]
-    },
     {
      "name": "mkIsQueryGroup",
      "description": "True for a group node (as opposed to a rule).",
@@ -3382,6 +3373,21 @@
     }
    ]
   },
+  {
+   "name": "core/signal-forms",
+   "import": "@mk-kit/ui/core/signal-forms",
+   "exports": [
+    {
+     "name": "mkInjectFieldTouched",
+     "description": "Touched-gate for a control's `invalid` input under Signal Forms.\n\nWhen a control is bound with the `[formField]` directive, Angular writes the\nfield's `invalid()` state straight into the control's `invalid` input — from\nthe first render, before the user has reached the field. mk-kit controls\npass that input through this gate so the invalid visual (and `aria-invalid`)\nonly shows once the field is touched or dirty, matching how `mk-form-field`\nreveals its message and how `submit()` (which marks every field touched)\nsurfaces the remaining problems.\n\nReturns a signal that is always `true` for a control that is not bound with\n`[formField]`, so a standalone `[invalid]=\"true\"` keeps working as before.\nCall it in a field initializer (an injection context):\n\n```ts\nprivate readonly fieldTouched = mkInjectFieldTouched();\nprotected readonly isInvalid = computed(\n  () => (this.invalid() && this.fieldTouched()) || (this.field?.hasError() ?? false),\n);\n```\n\nThe binding is looked up lazily, on first read: the `FormField` directive\nitself injects the element's `NG_VALUE_ACCESSOR` (the control) while it is\ncreated, so resolving it from the control's constructor would be circular.",
+     "file": "projects/mk-kit/core/signal-forms/signal-field.ts",
+     "kind": "function",
+     "signatures": [
+      "(): Signal<boolean>"
+     ]
+    }
+   ]
+  },
   {
    "name": "icon",
    "import": "@mk-kit/ui/icon",

package/data/llms-full.txt

@@ -1,4 +1,4 @@
-# @mk-kit/ui 0.51.0 — full API reference
+# @mk-kit/ui 0.52.0 — full API reference
 
 Generated from the library sources. Browsable version: https://mk-kit.dev/api · JSON: https://mk-kit.dev/api.json · Guides: https://mk-kit.dev/llms.txt
 
@@ -12,7 +12,7 @@ Every component and directive below is standalone — import the class from its
 
 ## @mk-kit/ui/core
 
-81 exports. `import { … } from '@mk-kit/ui/core';`
+80 exports. `import { … } from '@mk-kit/ui/core';`
 
 ### MkAnchoredPanel (directive)
 
@@ -346,39 +346,6 @@ still highlighted token-by-token (the editor validates separately).
 function mkHighlightJson(src: string): string
 ```
 
-### mkInjectFieldTouched (function)
-
-Import: `import { mkInjectFieldTouched } from '@mk-kit/ui/core';`
-
-Touched-gate for a control's `invalid` input under Signal Forms.
-
-When a control is bound with the `[formField]` directive, Angular writes the
-field's `invalid()` state straight into the control's `invalid` input — from
-the first render, before the user has reached the field. mk-kit controls
-pass that input through this gate so the invalid visual (and `aria-invalid`)
-only shows once the field is touched or dirty, matching how `mk-form-field`
-reveals its message and how `submit()` (which marks every field touched)
-surfaces the remaining problems.
-
-Returns a signal that is always `true` for a control that is not bound with
-`[formField]`, so a standalone `[invalid]="true"` keeps working as before.
-Call it in a field initializer (an injection context):
-
-```ts
-private readonly fieldTouched = mkInjectFieldTouched();
-protected readonly isInvalid = computed(
-  () => (this.invalid() && this.fieldTouched()) || (this.field?.hasError() ?? false),
-);
-```
-
-The binding is looked up lazily, on first read: the `FormField` directive
-itself injects the element's `NG_VALUE_ACCESSOR` (the control) while it is
-created, so resolving it from the control's constructor would be circular.
-
-```ts
-function mkInjectFieldTouched(): Signal<boolean>
-```
-
 ### mkIsQueryGroup (function)
 
 Import: `import { mkIsQueryGroup } from '@mk-kit/ui/core';`
@@ -1605,6 +1572,43 @@ Visual treatment for tinted/interactive surfaces.
 type MkVariant = 'solid' | 'soft' | 'outline' | 'ghost' | 'link';
 ```
 
+## @mk-kit/ui/core/signal-forms
+
+1 exports. `import { … } from '@mk-kit/ui/core/signal-forms';`
+
+### mkInjectFieldTouched (function)
+
+Import: `import { mkInjectFieldTouched } from '@mk-kit/ui/core/signal-forms';`
+
+Touched-gate for a control's `invalid` input under Signal Forms.
+
+When a control is bound with the `[formField]` directive, Angular writes the
+field's `invalid()` state straight into the control's `invalid` input — from
+the first render, before the user has reached the field. mk-kit controls
+pass that input through this gate so the invalid visual (and `aria-invalid`)
+only shows once the field is touched or dirty, matching how `mk-form-field`
+reveals its message and how `submit()` (which marks every field touched)
+surfaces the remaining problems.
+
+Returns a signal that is always `true` for a control that is not bound with
+`[formField]`, so a standalone `[invalid]="true"` keeps working as before.
+Call it in a field initializer (an injection context):
+
+```ts
+private readonly fieldTouched = mkInjectFieldTouched();
+protected readonly isInvalid = computed(
+  () => (this.invalid() && this.fieldTouched()) || (this.field?.hasError() ?? false),
+);
+```
+
+The binding is looked up lazily, on first read: the `FormField` directive
+itself injects the element's `NG_VALUE_ACCESSOR` (the control) while it is
+created, so resolving it from the control's constructor would be circular.
+
+```ts
+function mkInjectFieldTouched(): Signal<boolean>
+```
+
 ## @mk-kit/ui/icon
 
 8 exports. `import { … } from '@mk-kit/ui/icon';`

package/data/llms.txt

@@ -1,6 +1,6 @@
 # mk-kit
 
-> Themable, accessible Angular 22 component library for admin dashboards and UIs. Signals-based, WCAG 2.1 AA, controlled entirely through CSS variables with light/dark out of the box. — `@mk-kit/ui` 0.51.0. 169 components, 41 directives, 16 services and 144 helper functions across 29 tree-shakeable entry points. MIT licensed, zero runtime dependencies beyond Angular. Standalone components, signals, OnPush, zoneless-ready, SSR-safe, RTL and i18n via `provideMkI18n`.
+> Themable, accessible Angular 22 component library for admin dashboards and UIs. Signals-based, WCAG 2.1 AA, controlled entirely through CSS variables with light/dark out of the box. — `@mk-kit/ui` 0.52.0. 169 components, 41 directives, 16 services and 144 helper functions across 30 tree-shakeable entry points. MIT licensed, zero runtime dependencies beyond Angular. Standalone components, signals, OnPush, zoneless-ready, SSR-safe, RTL and i18n via `provideMkI18n`.
 
 Install with `ng add @mk-kit/ui` (or `npm i @mk-kit/ui` + import `@mk-kit/ui/styles/mk-kit.css`). Import from the group entry points (`@mk-kit/ui/forms`, `@mk-kit/ui/table`, …) so each lazy chunk only carries what it uses; the root `@mk-kit/ui` entry re-exports everything. Every component is standalone: add the class to a component's `imports`. Theme with `--mk-*` CSS custom properties; `MkThemeService` switches light/dark/system and density.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mk-kit/mcp",
-  "version": "0.51.0",
+  "version": "0.52.0",
   "description": "MCP server for @mk-kit/ui — lets AI coding assistants look up every component, directive, service and helper of the mk-kit Angular library (inputs, outputs, methods, import paths, docs links).",
   "license": "MIT",
   "type": "module",