ngxsmk-datepicker 1.9.29 → 2.0.2

package/README.md

@@ -7,7 +7,7 @@
 
 **npm i ngxsmk-datepicker**
 
-> **Stable Version**: `1.9.28` is the current stable release. For production use, install the latest version from npm.
+> **Stable Version**: `2.0.2` is the current stable release. For production use, install the latest version from npm.
 > 
 > ⚠️ **Warning**: Version `1.9.26` contains broken styles. If you are using `1.9.26`, please upgrade to `1.9.28` or downgrade to `1.9.25` immediately.
 

package/docs/API.md

@@ -39,7 +39,7 @@ import { NgxsmkDatepickerComponent } from 'ngxsmk-datepicker';
 |-------|------|---------|--------|-------------|---------|
 | `mode` | `'single' \| 'range' \| 'multiple'` | `'single'` | Stable | Selection mode | `mode="single"` or `[mode]="'range'"` |
 | `value` | `DatepickerValue` | `null` | Stable | Current value (one-way binding) | `[value]="selectedDate"` |
-| `field` | `any` | `null` | Stable | Signal form field (Angular 21+). Automatically tracks dirty state when using `[field]` binding. | `[field]="myForm.dateField"` |
+| `field` | `SignalFormField \| SignalFormFieldConfig` | `null` | Stable | Signal form field (Angular 21+). Automatically tracks dirty state when using `[field]` binding. Supports direct signals, signals with properties, and resolution of nested signals. | `[field]="myForm.dateField"` |
 | `placeholder` | `string \| null` | `'Select Date'` or `'Select Time'` | Stable | Input placeholder text | `placeholder="Choose a date"` |
 | `inputId` | `string` | `''` | Stable | Custom ID for the input element | `inputId="my-date-input"` |
 | `name` | `string` | `''` | Stable | Name attribute for the input element | `name="my-date-field"` |
@@ -2179,6 +2179,34 @@ type DateInput =
   | { toDate: () => Date; _isAMomentObject?: boolean; $d?: Date };
 ```
 
+
+### SignalFormField (v2.0.2+)
+
+**Status**: Stable
+
+Type representing a signal-based form field.
+
+```typescript
+type SignalFormField = any; // Compatible with Angular 21 FieldTree
+```
+
+### SignalFormFieldConfig (v2.0.2+)
+
+**Status**: Stable
+
+Interface for a resolved or direct signal form field configuration.
+
+```typescript
+interface SignalFormFieldConfig {
+  value: Signal<DatepickerValue> | WritableSignal<DatepickerValue> | (() => DatepickerValue);
+  disabled: Signal<boolean> | (() => boolean) | boolean;
+  required?: Signal<boolean> | (() => boolean) | boolean;
+  setValue?: (value: DatepickerValue) => void;
+  updateValue?: (updater: (prev: DatepickerValue) => DatepickerValue) => void;
+  markAsDirty?: () => void;
+  errors?: Signal<ValidationError[]> | (() => ValidationError[]);
+}
+
 ### DatepickerHooks
 
 **Status**: Stable (v1.9.22+)

package/docs/signal-forms.md

@@ -113,6 +113,29 @@ export class TwoWayComponent {
 }
 ```
 
+### Signal Field Resolution (v2.0.2+)
+
+The datepicker includes a robust resolution mechanism for signal-based fields. It can handle:
+- **Direct Signals**: A signal that contains the field configuration.
+- **Signals with Properties**: A signal function that has field properties (like `value`, `disabled`, `setValue`) attached directly to it (common in some Signal Form implementations).
+- **Nested Signals**: Signals that return a field configuration object when executed.
+
+The datepicker intelligently detects these patterns and unwraps them automatically.
+
+### Enhanced Type Safety
+
+The library now exports `SignalFormFieldConfig` to allow you to strictly type your field configurations:
+
+```typescript
+import { SignalFormFieldConfig } from 'ngxsmk-datepicker';
+
+const config: SignalFormFieldConfig = {
+  value: signal(new Date()),
+  disabled: () => false,
+  required: true
+};
+```
+
 ## Dirty State Tracking
 
 When using the `[field]` binding, the datepicker automatically tracks the form's dirty state. The form will be marked as dirty when a user selects a date: