@frame-kit/ui-ng 0.2.7 → 0.2.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@frame-kit/ui-ng",
-  "version": "0.2.7",
+  "version": "0.2.8",
   "description": "Style-agnostic, token-driven Angular UI component library for FrameKit.",
   "license": "MIT",
   "repository": {

package/types/frame-kit-ui-ng-forms.d.ts

@@ -1,5 +1,5 @@
 import * as _angular_core from '@angular/core';
-import { InjectionToken, TemplateRef, Type, OnInit, ElementRef } from '@angular/core';
+import { InjectionToken, AfterContentInit, TemplateRef, Type, OnInit, ElementRef } from '@angular/core';
 import { NgControl, AsyncValidatorFn, ValidatorFn, AbstractControl, FormArray, FormGroup, FormControl, ControlValueAccessor } from '@angular/forms';
 import { IconSize, IconColor } from '@frame-kit/ui-ng/core/icon';
 
@@ -185,7 +185,7 @@ declare class FkSuffixDirective {
     static ɵdir: _angular_core.ɵɵDirectiveDeclaration<FkSuffixDirective, "[fkSuffix]", never, {}, {}, never, never, true, never>;
 }
 
-declare class FormFieldComponent {
+declare class FormFieldComponent implements AfterContentInit {
     readonly className: _angular_core.InputSignal<string>;
     /** Text label rendered above the field; forwarded to the projected fk-label when present. */
     readonly label: _angular_core.InputSignal<string | null>;
@@ -218,6 +218,21 @@ declare class FormFieldComponent {
     readonly suffixRef: _angular_core.Signal<FkSuffixDirective | undefined>;
     private readonly globalErrorMessages;
     private readonly cdr;
+    private readonly host;
+    /**
+     * `fkPrefix` and `fkSuffix` project only when their directive resolves, and
+     * it only resolves when the consumer imports it. Forget the import and the
+     * attribute stays inert markup: Angular does not warn about an unknown
+     * attribute on a known element, the content query returns undefined, the
+     * wrapper is never rendered, and the icon simply is not there. Nothing fails
+     * — which is what makes it slow to diagnose.
+     *
+     * Content queries have resolved by this point, and the element is still in
+     * the DOM either way, so an element carrying the attribute with no resolved
+     * directive is an unambiguous signal.
+     */
+    ngAfterContentInit(): void;
+    private warnOnUnresolvedProjection;
     get hostClass(): string;
     readonly fieldId: string;
     readonly labelId: string;