ngxsmk-datepicker 2.1.3 → 2.1.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md ADDED
@@ -0,0 +1,1092 @@
1
+ # Changelog
2
+
3
+ All notable changes to this project will be documented in this file.
4
+
5
+ **Last updated:** February 2026 · **Current stable:** v2.1.6
6
+
7
+ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
8
+ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
9
+
10
+ ## [2.1.6] - 2026-02-17
11
+
12
+ ### Changed
13
+
14
+ - **Version**: Bump to 2.1.6 (current stable release).
15
+
16
+ ## [2.1.5] - 2026-02-17
17
+
18
+ ### Added
19
+
20
+ - **Validation messages (i18n)**: New user-facing validation strings in `DatepickerTranslations`—`invalidDateFormat`, `dateBeforeMin`, `dateAfterMax`, `invalidDate`—with full translation support across all 8 languages. The component shows a translated error message when input is invalid, before min, or after max, and emits `validationError` with `code` and `message`.
21
+ - **Calendar loading state**: Visual loading state (spinner + text) while the calendar is opening or generating. Loading state is announced to screen readers via `AriaLiveService`. A public getter is available for templates to reflect "calendar is loading."
22
+ - **Installation options**: New `docs/INSTALLATION.md` documenting all install methods (npm, Yarn, pnpm, Bun, Git, local path, CDN, tarball). Demo Installation page updated with alternative install commands and a link to the full guide.
23
+ - **Issue-reproduction app**: New minimal Angular app `angular-issue-test` (routes: Home, month-navigation, range-reselection) for manually verifying reported issues. Served via `npx ng serve angular-issue-test`.
24
+
25
+ ### Changed
26
+
27
+ - **Version**: Bump to 2.1.5 (stable release).
28
+ - **Demo app – light/dark theme**: Theme toggle now correctly switches the UI. `data-theme` is synced on the document when theme changes; `html[data-theme='light']` CSS overrides added for the light palette. Nav-link hover uses `var(--color-text-main)` for both themes. Responsive spacing variables use `clamp()`.
29
+ - **Library refactors**: Calendar grid generation and input parsing/formatting logic extracted into `CalendarGenerationService` and `DatepickerParsingService` respectively.
30
+ - **Demo styles**: New utility classes (e.g. `.link`, `.no-underline`, `.text-dim`, `.gap-xs`) and tip label layout tweak.
31
+ - **Docs**: README and library README reference `docs/INSTALLATION.md`. CHANGELOG, MIGRATION, ROADMAP, SECURITY, API_REFERENCE, BUNDLE_SIZE_REPORT, and API.md updated for 2.1.5.
32
+
33
+ ### Fixed
34
+
35
+ - **Demo theme**: Fixed light/dark theme toggle not applying—demo now correctly reflects the active theme (header toggle and system preference).
36
+
37
+ ## [2.1.4] - 2026-02-13
38
+
39
+ ### Added
40
+
41
+ - **Playground Enhancements**: Added new configuration options for `minDate`, `maxDate`, and `weekStart` to the interactive playground, allowing users to test boundary constraints and locale overrides.
42
+ - **Improved Internationalization**: Added full translation support for new playground features across all 8 supported languages (English, German, Spanish, Swedish, Korean, Chinese, Japanese, and French).
43
+
44
+ ### Fixed
45
+
46
+ - **Calendar Grid Consistency**: Ensured the calendar always generates a full 42-day (6-week) grid. This prevents layout shifts and provides a more stable UI when navigating between months with different numbers of days.
47
+ - **Locale-Specific Week Starts**: Fixed issues with manual `weekStart` overrides and locale-dependent first day of week calculations, ensuring accurate calendar generation across diverse cultural settings.
48
+
49
+ ## [2.1.3] - 2026-02-11
50
+
51
+ ### Fixed
52
+
53
+ - **Inline Datepicker Width**: Fixed an issue where the inline datepicker was constrained by container styles in some contexts, causing it to appear cramped or cut off. The inline mode now correctly fits its content.
54
+
55
+ ## [2.1.2] - 2026-02-11
56
+
57
+ ### Fixed
58
+
59
+ - **Mobile Experience**: Improved stability on mobile devices (specifically Samsung/Android/Edge).
60
+ - Fixed an issue where the calendar would close prematurely during interactions due to portaling logic.
61
+ - Added "ghost click" protection to the backdrop to prevent accidental closure right after opening.
62
+ - Standardized containment checks to handle popovers appended to the document body.
63
+ - **Circular Dependency**: Resolved `RuntimeError: NG0200: Circular dependency detected` when using `NgModel` or Reactive Forms.
64
+ - Removed `NG_VALUE_ACCESSOR` from component providers to break the circular link with `NgControl`.
65
+ - Implemented manual `valueAccessor` assignment in the constructor for safe interaction with Angular's form system.
66
+ - **Dependency Cleanup**: Removed unused `forwardRef` and `NG_VALUE_ACCESSOR` imports to improve bundle size and build performance.
67
+
68
+ ### Changed
69
+
70
+ - **UI Refinement (Premium Aesthetic)**: Improved the overall visual appearance with a "border detox."
71
+ - Reduced border thickness from 1.5px to 1px library-wide.
72
+ - Softened border colors and added subtle ghost backgrounds for interactive elements.
73
+ - Enhanced navigation buttons with a borderless-by-default look.
74
+
75
+ ### Removed
76
+
77
+ - **Range Duration Header**: Removed the "X Days" duration header from range selection mode to reduce visual clutter and simplify the UI.
78
+
79
+
80
+ ## [2.1.1] - 2026-02-09
81
+
82
+ ### Fixed
83
+
84
+ - **Material Form Field Integration**: Improved `NgxsmkDatepickerComponent` to correctly notify `mat-form-field` of state changes.
85
+ - Injected `NgControl` into the component to properly integrate with Angular's form system.
86
+ - Added `stateChanges.next()` call in `emitValue` to ensure the form field reflects internal state changes (e.g., when selecting a date).
87
+ - **Helper Function Enhancements**: Updated `provideMaterialFormFieldControl` with runtime warnings for missing or incorrect Material tokens.
88
+
89
+ ## [2.1.0] - 2026-02-05
90
+
91
+
92
+ ### Fixed
93
+
94
+ - **Package Configuration**: Corrected TypeScript declaration paths in package.json
95
+ - Updated `types` and `typings` fields to point to `types/ngxsmk-datepicker.d.ts` instead of non-existent `index.d.ts`
96
+ - Simplified `exports` field to match v2.0.9 format, removing unnecessary module export configurations
97
+ - Removed disallowed `esm2022` property from package.json
98
+ - Ensures proper TypeScript module resolution in consuming applications
99
+
100
+ ### Changed
101
+
102
+ - **Package Distribution**: Streamlined package exports configuration for better compatibility
103
+ - Aligned exports structure with stable v2.0.9 format
104
+ - Removed redundant module resolution entries for cleaner package.json
105
+
106
+ ### Important Notice
107
+
108
+ ⚠️ **Versions 2.0.10 and 2.0.11 have been unpublished from npm** due to critical package configuration issues that prevented proper TypeScript module resolution. All users should upgrade to v2.1.1 or later.
109
+
110
+ ## [2.0.11] - 2026-02-05 [BROKEN - UNPUBLISHED]
111
+
112
+ **⚠️ This version has been unpublished from npm due to incorrect package configuration. Use v2.1.1 instead.**
113
+
114
+ ### Fixed
115
+
116
+ - **TypeScript Type Declarations**: Attempted to fix "Could not find a declaration file for module 'ngxsmk-datepicker'" error
117
+ - Added proper `exports` field in package.json with correct type declaration path
118
+ - Configured exports to point to `index.d.ts` for TypeScript module resolution
119
+ - **Note**: This fix was incomplete and the version has been replaced by v2.1.1
120
+
121
+ ## [2.0.10] - 2026-02-05 [BROKEN - UNPUBLISHED]
122
+
123
+ **⚠️ This version has been unpublished from npm due to incorrect package configuration. Use v2.1.1 instead.**
124
+
125
+ ### Fixed
126
+
127
+ - **Infinite Recursion in Date Utilities**: Fixed `RangeError: Maximum call stack size exceeded` in `getEndOfDay()` function
128
+ - Refactored recursive logic to use direct date manipulation
129
+ - Replaced recursive `addMonths` calls with iterative approach
130
+ - Improves performance and eliminates stack overflow risk
131
+ - **Timezone Test Edge Cases**: Fixed date component preservation in timezone conversion tests
132
+ - Updated timezone tests to use `Date.UTC()` for consistent cross-environment behavior
133
+ - Ensures test reliability across different system timezones with non-integer offsets (UTC+5:30, etc.)
134
+
135
+ ### Optimized
136
+
137
+ - **Build and Release**: Removed unnecessary generated files from distribution
138
+ - Cleaned up coverage reports and build artifacts
139
+ - Streamlined demo app output
140
+
141
+ ## [2.0.9] - 2026-01-31
142
+
143
+ ### Optimized
144
+
145
+ - **Stylesheet Architecture**: Comprehensive optimization of CSS assets
146
+ - Replaced redundant mobile stylesheets with a unified "Responsive Overrides" system
147
+ - Removed deprecated keyframes and duplicate selectors
148
+ - Enhanced commenting standards with industrial/professional documentation style
149
+ - Reduced CSS bundle size by eliminating unused styles
150
+
151
+ ### Fixed
152
+
153
+ - **Sticky Header Overlap**: Resolved critical z-index stacking issue where sticky headers would overlap the datepicker popup
154
+ - Implemented aggressive z-index boost (`2147483647`) for the host component when active
155
+ - Ensures datepicker always floats above application navigation bars and modal backdrops
156
+ - **Mobile Dropup Positioning**: Fixed footer clipping issues on mobile devices
157
+ - Time selection dropdowns now intelligently open upwards ("dropup") on screens < 992px
158
+ - Prevents dropdown options from being cut off by the bottom of the viewport or sticky footers
159
+ - Improved touch interactions for time selection on mobile
160
+
161
+ ## [2.0.8] - 2026-01-31
162
+
163
+ ### Added
164
+
165
+ - **Ionic Integration**: Added automatic support for Ionic CSS variables
166
+ - Datepicker now automatically inherits Ionic app theme colors (primary, background, text)
167
+ - No additional configuration required for native look and feel in Ionic apps
168
+ - Documented integration steps in README
169
+
170
+ ### Optimized
171
+
172
+ - **Change Detection**: Optimized internal change detection strategy
173
+ - Removed redundant `ChangeDetectorRef` calls in favor of Signal-based updates
174
+ - Improved compatibility with Zoneless Angular applications
175
+ - Cleaner and more efficient state management
176
+
177
+ ### Fixed
178
+
179
+ - **Mobile Page Jump**: Fixed issue where selecting a date would cause the page to jump to the top on some mobile browsers (Firefox Android)
180
+ - Added `{ preventScroll: true }` to focus restoration logic
181
+ - **Dropdown Scrolling**: Fixed UX issue in month/year dropdowns
182
+ - Dropdowns now automatically scroll to the currently selected option when opened
183
+ - Improved mobile scrolling behavior within dropdowns by removing conflicting close logic
184
+
185
+ ### Changed
186
+
187
+ - **Version Update**: Updated to version 2.0.8
188
+
189
+ ## [2.0.7] - 2026-01-26
190
+
191
+ - **Version Update**: Updated to version 2.0.7
192
+
193
+ ## [2.0.6] - 2026-01-15
194
+
195
+ ### Enhanced
196
+
197
+ - **Range Picker Reselection**: Improved comprehensive range reselection behavior
198
+ - Clicking the start date when a complete range is selected now clears only the end date
199
+ - Clicking the end date when a complete range is selected now clears the start date and sets the end date as the new start date
200
+ - **NEW**: Clicking any date within the selected range now clears the end date and sets the clicked date as the new start date
201
+ - Allows users to easily redefine date ranges from any point (start, end, or within the range)
202
+ - Example scenarios:
203
+ - Range: Jan 10 - Jan 20, Click Jan 10 → Result: Jan 10 (can select new end)
204
+ - Range: Jan 10 - Jan 20, Click Jan 20 → Result: Jan 20 (can select new end)
205
+ - Range: Jan 26 - Jan 30, Click Jan 27 → Result: Jan 27 (can select new end)
206
+ - Improves usability by providing intuitive range adjustment from any direction
207
+
208
+ ### Changed
209
+
210
+ - **Code Cleanup**: Removed unnecessary inline comments from range selection logic for cleaner, more maintainable code
211
+ - **Version Update**: Updated to version 2.0.6
212
+
213
+ ## [2.0.5] - 2026-01-15
214
+
215
+ ### Enhanced
216
+
217
+ - **Range Picker Reselection**: Improved user experience when reselecting date ranges
218
+ - Clicking the start date again after selecting a complete range now clears only the end date
219
+ - Allows users to easily redefine the end date without clearing the entire selection
220
+ - The start date remains selected, and users can immediately choose a new end date
221
+ - Example: After selecting Jan 19 (start) → Jan 21 (end), clicking Jan 19 again keeps Jan 19 selected and clears Jan 21
222
+ - Improves usability by reducing clicks needed to adjust date ranges
223
+
224
+ ### Fixed
225
+
226
+ - **Range Mode Value Emission**: Fixed issue where clicking the start date again after a complete range was selected would update the visual state but not emit the value change
227
+ - The datepicker now properly emits a partial range value (`{ start: Date, end: null }`) when the end date is cleared
228
+ - Parent components and form bindings now correctly reflect the cleared end date state
229
+ - Resolves inconsistency between visual calendar state and bound values
230
+
231
+ ### Patch Changes
232
+
233
+ - **Version Update**: Updated to version 2.0.5
234
+ - **Documentation**: Added comprehensive "Form Validation" section to README to explain `readonly` input behavior and provide solutions for native browser validation (e.g., using `allowTyping="true"`).
235
+
236
+ ## [2.0.4] - 2026-01-14
237
+
238
+ ### Patch Changes
239
+
240
+ - **Version Update**: Updated to version 2.0.4
241
+ - **Validation Fix**: Fixed issue where `[field]` validation messages were not triggering because the `touched` state was not being synced to the field. Added `markAsTouched` support to `FieldSyncService` and updated `NgxsmkDatepickerComponent` to mark the field as touched on blur and value selection.
242
+
243
+ ## [2.0.3] - 2026-01-14
244
+
245
+ ### Patch Changes
246
+
247
+ - **Version Update**: Updated to version 2.0.3
248
+ - **Code Cleanup**: Removed unnecessary comments from `field-sync.service.ts` to improve code readability and maintainability.
249
+ - **Bug Fixed**: Verified fixes for issues #136, #112, #84, and #71.
250
+ - **TypeScript Compatibility**: Fixed `SignalFormField` and `SignalFormFieldConfig` types to be fully compatible with Angular 21+ `FieldTree<string | Date | null, string>` structure. The types now accept `WritableSignal<string | Date | null>` from Angular's Signal Forms, resolving TypeScript compilation errors when using `[field]` binding.
251
+
252
+ ## [2.0.2] - 2026-01-14
253
+
254
+ ### Patch Changes
255
+
256
+ - **Version Update**: Updated to version 2.0.2
257
+ - **Documentation**: Updated all documentation to reflect new version
258
+
259
+ ## [2.0.1] - 2026-01-14
260
+
261
+ ### Patch Changes
262
+
263
+ - **Version Update**: Updated to version 2.0.1
264
+ - **Bug Fixes**: Minor bug fixes and improvements
265
+ - **Documentation**: Updated all documentation to reflect new version
266
+
267
+ ## [2.0.0] - 2026-01-14
268
+
269
+ ### Major Changes
270
+
271
+ - **Version Update**: Updated to version 2.0.0
272
+ - **Breaking Changes**:
273
+ - Updated minimum Angular version requirement to 17.0.0
274
+ - Improved Signal Forms integration
275
+ - Enhanced timezone handling
276
+ - **Documentation**: Updated all documentation to reflect new version
277
+
278
+ ## [1.9.29] - 2026-01-13
279
+
280
+ ### Added
281
+
282
+ - **Angular Signal Forms Validation Support**: Full support for schema-based validation with Angular 21+ Signal Forms
283
+ - Automatically detects and responds to validation errors from the field's `errors()` signal
284
+ - Recognizes `required` validation from schema (e.g., `required(p.dateDue)`)
285
+ - Updates component's `errorState` based on field's `invalid()` signal
286
+ - Reactive updates when validation state changes
287
+ - Resolves [#136](https://github.com/NGXSMK/ngxsmk-datepicker/issues/136) - "datepicker doesn't recognise 'required' attribute in schema"
288
+ - **Validation Error Types**: Added `ValidationError` interface to support Angular Signal Forms error structure
289
+ - **Error State Callback**: Added `onErrorStateChanged` callback to `FieldSyncCallbacks` for validation state tracking
290
+ - **Comprehensive Documentation**: Added `docs/SIGNAL_FORMS_VALIDATION.md` with usage examples, API reference, and migration guide
291
+ - **Test Coverage**: Added comprehensive test suite in `signal-forms-validation.spec.ts` for validation scenarios
292
+ - **Input Attributes Support**: Added support for standard input attributes on the datepicker input element
293
+ - `inputId`: Custom ID support (defaults to component unique ID)
294
+ - `name`: Form name attribute support
295
+ - `autocomplete`: Autocomplete attribute support (defaults to 'off')
296
+ - `aria-invalid`: Accessibility support for invalid state visibility
297
+ - **Keyboard Shortcuts Help Dialog**: Added a built-in help dialog for keyboard shortcuts, accessible via `?` or `Shift + /`.
298
+ - **New Shortcut**: Added `?` keyboard shortcut to toggle the help dialog.
299
+
300
+ ### Enhanced
301
+
302
+ - **Field Sync Service**: Enhanced with new helper methods
303
+ - `readFieldErrors()`: Reads validation errors from field's `errors` signal
304
+ - `readRequiredState()`: Checks for required validation in errors or direct property (prioritizes schema validation)
305
+ - `hasValidationErrors()`: Determines if field has any validation errors
306
+ - **Backward Compatibility**: Maintains full compatibility with:
307
+ - Direct `required` attribute: `<ngxsmk-datepicker required>`
308
+ - Reactive Forms: `<ngxsmk-datepicker [formControl]="dateControl">`
309
+ - Template-driven forms: `<ngxsmk-datepicker [(ngModel)]="date">`
310
+ - Direct `required` property on field: `field.required = true`
311
+
312
+ ### Fixed
313
+
314
+ - **Header Layout**: Fixed CSS issue where the datepicker header width was not spanning the full container width, ensuring consistent layout across all screen sizes.
315
+ - **Angular Signal Forms Schema Validation**: Fixed issue where `required` attribute from schema was not properly reflected on the input and form validation
316
+ - **Month Navigation**: Fixed a critical bug where navigating to the next month would skip a month (e.g., Jan -> Mar) if the current date was the 31st (due to JS Date overflow). Navigation now correctly calculates from the start of the month.
317
+ - **Signal Forms Integration**: Critical fix for `[field]` binding where Signal fields (passed as functions) were being ignored, preventing validation metadata (like `.required`) from being read.
318
+ - **Range Navigation**: Fixed usability issue where selecting an end date in a different month would unexpectedly reset the calendar view back to the start date's month, causing confusion.
319
+ - **Field Sync Service**: Updated `readRequiredState` and `readDisabledState` to correctly process function-type fields (Signals).
320
+
321
+ ### Changed
322
+
323
+ - **Version Update**: Updated to version 1.9.29
324
+
325
+ ## [1.9.27] - 2026-01-10
326
+
327
+ ### Refactored
328
+
329
+ - **Modern Control Flow**: Fully migrated all standalone components (`NgxsmkDatepickerComponent`, `CalendarHeaderComponent`, `CalendarMonthViewComponent`, `CalendarYearViewComponent`, `TimeSelectionComponent`, `CustomSelectComponent`) to modern Angular `@if` and `@for` block syntax.
330
+ - **Optimized Imports**: Replaced monolithic `CommonModule` with individual directive and pipe imports (`NgClass`, `NgTemplateOutlet`, `DatePipe`) in all standalone components. This improves tree-shaking and resolves resolution conflicts in some environments.
331
+
332
+ ### Fixed
333
+
334
+ - **Module Resolution**: Resolved "Value could not be determined statically" error when importing standalone library components into traditional NgModules in some monorepo configurations.
335
+ - **Build Process**: Fixed library compilation error (`TS6133`) caused by unused `CommonModule` after migration to modern control flow.
336
+ - **Monorepo Compatibility**: Improved Angular core dependency resolution for example applications to prevent "duplicate symbol" and "exported symbol not found" errors during development.
337
+
338
+ ### Maintenance
339
+
340
+ - **Git**: Added `/examples` directory to `.gitignore` to prevent committing experimental test applications.
341
+
342
+ ### Changed
343
+
344
+ - **Version Update**: Updated to version 1.9.27
345
+
346
+ ## [1.9.26] - 2026-01-09
347
+
348
+ > ⚠️ **DO NOT USE**: This version contains broken styles. Please use v1.9.27 or v1.9.25 instead.
349
+
350
+ ### Refactored
351
+
352
+ - **Core Architecture**: Major refactoring of `NgxsmkDatepickerComponent` to address "God Component" issues
353
+ - Split monolithic component into dedicated sub-components: `CalendarMonthViewComponent`, `CalendarYearViewComponent`
354
+ - Integrated `CalendarHeaderComponent` and `TimeSelectionComponent` to handle specific functional areas
355
+ - Removed 1000+ lines of inline template code, significantly improving maintainability and readability
356
+ - Improved strict template type checking support
357
+ - **No breaking changes** to the public API
358
+
359
+ ### Fixed
360
+
361
+ - **Ionic Integration**: Fixed issue where `ionic-integration.css` was not exported in the package bundle
362
+ - Moved styles to allow correct exporting via package logic
363
+ - Ensures `@import 'ngxsmk-datepicker/styles/ionic-integration.css'` works as documented
364
+ - Resolves [#123](https://github.com/NGXSMK/ngxsmk-datepicker/issues/123)
365
+
366
+ ### Fixed (Mobile UI)
367
+
368
+ - **Mobile View Styles**: Enhanced mobile UI styles for both Angular and Ionic projects
369
+ - Added proper positioning and animations for `bottom-sheet` and `fullscreen` mobile modes
370
+ - Fixed missing styles in core `datepicker.css` that prevented `mobileModalStyle` from working correctly
371
+ - Improved gesture handling and transition animations for mobile devices
372
+
373
+ ### Changed
374
+
375
+ - **Version Update**: Updated to version 1.9.26
376
+
377
+ ## [1.9.25] - 2026-01-06
378
+
379
+ ### Fixed
380
+
381
+ - **IDE Support**: Fixed "This component requires inline template type-checking" error by including all source files in tsconfig
382
+ - Ensures accurate template type checking in VS Code and other IDEs
383
+ - **NPM Package**: Fixed issue where `README.md` was missing from the npm package
384
+ - Updated build scripts to ensure `README.md` is correctly included in the distribution
385
+ - Ensures proper documentation rendering on npmjs.com
386
+
387
+ ### Changed
388
+
389
+ - **Version Update**: Updated to version 1.9.25
390
+
391
+ ## [1.9.23] - 2025-12-15
392
+
393
+ ### Fixed
394
+
395
+ - **Signal Forms Dirty State Tracking (Issue #112)**: Fixed issue where Angular Signal Forms were not being marked as dirty when date values changed through the `[field]` binding
396
+ - Improved `updateFieldFromInternal()` method to always prefer `setValue()` and `updateValue()` methods over direct signal mutation
397
+ - Added dev mode warnings when falling back to direct signal mutation, which may bypass dirty state tracking
398
+ - Enhanced error handling to track which update method succeeded and provide better diagnostics
399
+ - The datepicker now properly marks forms as dirty when using `[field]` binding with Angular 21+ Signal Forms
400
+ - Added comprehensive test coverage for Signal Forms dirty state tracking
401
+ - Updated documentation with detailed guidance on proper usage patterns and troubleshooting
402
+ - Resolves [#112](https://github.com/NGXSMK/ngxsmk-datepicker/issues/112)
403
+
404
+ - **CSS Variables Theming (Issue #84)**: Fixed issue where CSS variables theming was not working when variables were defined in the global `:root` selector
405
+ - Enhanced CSS selector from `:root` to `:root, :root > body` for higher specificity
406
+ - Added `!important` flags to inline styles to ensure they override existing styles
407
+ - ThemeBuilderService now properly overrides global stylesheet variables
408
+ - Updated documentation to explain the fix and provide guidance
409
+ - Resolves [#84](https://github.com/NGXSMK/ngxsmk-datepicker/issues/84)
410
+
411
+ ### Changed
412
+
413
+ - **Version Update**: Updated to version 1.9.23
414
+
415
+ ## [1.9.22] - 2025-12-14
416
+
417
+ ### Fixed
418
+
419
+ - **Form Control Value Initialization**: Fixed issue where datepicker was not properly updating the displayed month when initialized with form control values
420
+ - Added `_updateMemoSignals()` call in `writeValue()` method to ensure month/year signals are properly updated
421
+ - Added `scheduleChangeDetection()` to trigger UI updates when form control values are set
422
+ - Ensures datepicker correctly displays the month from form control values instead of defaulting to current month
423
+ - Resolves issue where demo app datepickers were showing December instead of the correct month from form control values
424
+ - Fixes calendar month display when using Reactive Forms with initial values
425
+
426
+ - **Locale Week Start Detection**: Fixed `getFirstDayOfWeek()` function to properly return 1 for en-GB locale
427
+ - Added fallback logic for locales where `Intl.Locale.weekInfo` is not available (older browsers/environments)
428
+ - Implemented locale-based mapping for common locales (en-GB, en-AU, en-NZ, and most European locales return 1 for Monday)
429
+ - Now correctly returns Monday (1) for en-GB and other European locales
430
+ - Maintains backward compatibility with en-US and other locales that use Sunday (0) as first day
431
+ - All calendar utils tests now passing (19/19 tests)
432
+
433
+ ### Changed
434
+
435
+ - **Version Update**: Updated to version 1.9.22
436
+
437
+ ## [1.9.21] - 2025-12-10
438
+
439
+ ### Added
440
+
441
+ - **Mobile-Specific Features**: Comprehensive mobile optimization and native integration
442
+ - Native date picker integration with `useNativePicker` input for automatic native picker on mobile devices
443
+ - Bottom sheet modal style with swipe-to-dismiss gesture support
444
+ - Mobile-optimized time picker with enhanced touch interactions
445
+ - Enhanced gesture support: double-tap on today to select, swipe up/down for year navigation
446
+ - Haptic feedback support with `enableHapticFeedback` input (light, medium, heavy vibrations)
447
+ - Mobile keyboard optimizations for better input experience
448
+ - Mobile-specific animations and transitions
449
+ - Auto-detection of mobile devices with `autoDetectMobile` input
450
+ - Mobile modal styles: `bottom-sheet`, `center`, and `fullscreen` options
451
+
452
+ - **Advanced Selection Modes**: Extended selection capabilities beyond single/range/multiple
453
+ - Week selection mode: Select entire weeks with configurable week start day
454
+ - Month selection mode: Select entire months with start/end dates
455
+ - Quarter selection mode: Select quarters (Q1, Q2, Q3, Q4) with proper date ranges
456
+ - Year selection mode: Select entire years with January 1st to December 31st ranges
457
+ - All new modes work seamlessly with existing validation, constraints, and formatting
458
+
459
+ - **Enhanced Time Selection**: Improved time picker functionality
460
+ - Seconds selection with `showSeconds` input and `secondInterval` configuration
461
+ - `currentSecond` property for programmatic second control
462
+ - Infrastructure for time range selection (future enhancement)
463
+
464
+ - **Code Refactoring**: Improved maintainability and performance
465
+ - `CalendarGenerationService`: Extracted calendar generation logic for better separation of concerns
466
+ - `DisplayFormattingService`: Centralized display formatting logic with support for all selection modes
467
+ - `DateValidationService`: Extracted date validation logic for reusable validation across components
468
+ - Reduced main component size and complexity
469
+ - Improved code organization and testability
470
+
471
+ - **Accessibility Enhancements**: Improved screen reader and keyboard navigation
472
+ - Enhanced ARIA live region announcements with debouncing and queue management
473
+ - Improved focus trap management with proper focus return on close
474
+ - Better screen reader support for all new selection modes
475
+ - High contrast mode styling improvements
476
+
477
+ - **Performance Optimizations**: Infrastructure for better performance
478
+ - Virtual scrolling infrastructure for year/decade views (ready for future implementation)
479
+ - Lazy loading calendar months with intelligent caching (up to 24 months)
480
+ - Calendar month cache with automatic size management
481
+ - Preloading of adjacent months for smoother navigation
482
+
483
+ - **Test Coverage**: Comprehensive test suite updates
484
+ - New service tests: `CalendarGenerationService`, `DisplayFormattingService`, `DateValidationService`
485
+ - Updated comprehensive component tests with new selection modes
486
+ - Updated utility function tests for week/month/quarter/year helpers
487
+ - Updated E2E tests for mobile features and new selection modes
488
+ - All 414 tests passing with improved coverage
489
+
490
+ ### Changed
491
+
492
+ - **Version Update**: Updated to version 1.9.21
493
+ - **Hooks Interface**: Extended hooks interface to support new selection modes (`week`, `month`, `quarter`, `year`)
494
+ - **Type Definitions**: Updated `DatepickerValue` type to explicitly handle range mode with `[Date, Date | null]`
495
+ - **Service Architecture**: Refactored component to use new services for better maintainability
496
+
497
+ ### Fixed
498
+
499
+ - **Angular 21 Signal Forms Integration (Issue #80)**: Fixed broken `[field]` input binding with Angular 21 Signal Forms
500
+ - Improved signal detection in `readFieldValue()` to handle Angular 21's `FieldTree<Date, string>` structure
501
+ - Enhanced effect setup to properly track Signal Forms dependencies when `field.value` is a function returning a signal
502
+ - Fixed `updateFieldFromInternal()` to handle cases where `field.value` is a function that returns a writable signal
503
+ - Now correctly handles Angular 21 Signal Forms where `field.value` is a function that returns the actual signal
504
+ - Resolves [#80](https://github.com/NGXSMK/ngxsmk-datepicker/issues/80)
505
+ - **Build Issues**: Fixed TypeScript compilation errors related to strict null checks
506
+ - **Test Failures**: Fixed async timing issues in AriaLiveService tests
507
+ - **Calendar Generation**: Fixed structural issues in calendar generation method
508
+ - **Type Safety**: Improved type safety with explicit null checks and proper type definitions
509
+
510
+ ### Migration Notes
511
+
512
+ - This is a patch version update
513
+ - No breaking changes from v1.9.20
514
+ - All changes are backward compatible
515
+ - Compatible with Angular 17-22
516
+ - New features are opt-in and don't affect existing implementations
517
+ - Mobile features automatically detect mobile devices but can be disabled with `autoDetectMobile="false"`
518
+ - New selection modes extend existing `mode` input with additional options
519
+
520
+ ## [1.9.20] - 2025-12-06
521
+
522
+ ### Fixed
523
+
524
+ - **Test Environment Compatibility (Issue #71)**: Fixed `TypeError: window.matchMedia is not a function` error in test environments (jsdom/Vitest)
525
+ - Added try-catch block around `window.matchMedia` call in `applyAnimationConfig()` method
526
+ - Component now gracefully handles missing `matchMedia` API in test environments
527
+ - Prevents test failures when running with Vitest and jsdom
528
+ - Added comprehensive test coverage for `matchMedia` compatibility scenarios
529
+
530
+ ### Changed
531
+
532
+ - **Version Update**: Updated to version 1.9.20
533
+
534
+ ### Migration Notes
535
+
536
+ - This is a patch version update
537
+ - No breaking changes from v1.9.19
538
+ - All changes are backward compatible
539
+ - Compatible with Angular 17-22
540
+ - Fixes test compatibility issues with Vitest and jsdom environments
541
+
542
+ ## [1.9.19] - 2025-01-15
543
+
544
+ ### Added
545
+
546
+ - **Comprehensive Responsive Layout Redesign**: Complete redesign of demo project layout for all screen sizes
547
+ - Redesigned navbar for all breakpoints (320px-374px, 375px-479px, 480px-599px, 600px-767px, 768px-1023px, 1024px+)
548
+ - Enhanced sidebar navigation with mobile drawer, tablet collapsible, and desktop fixed layouts
549
+ - Responsive hero section with adaptive typography and button layouts
550
+ - Feature grid responsive design (1 column → 2 columns → 3 columns → 4 columns)
551
+ - Optimized content sections with responsive padding, typography, and spacing
552
+ - Improved example demo containers, code blocks, mobile preview containers, and result boxes
553
+ - Better touch targets and visual hierarchy across all breakpoints
554
+
555
+ ### Changed
556
+
557
+ - **Version Update**: Updated to version 1.9.19
558
+ - **Meta Tag Update**: Replaced deprecated `apple-mobile-web-app-capable` with `mobile-web-app-capable`
559
+ - **Code Cleanup**: Removed unnecessary comments from SCSS files for cleaner codebase
560
+
561
+ ### Migration Notes
562
+
563
+ - This is a patch version update
564
+ - No breaking changes from v1.9.18
565
+ - All changes are backward compatible
566
+ - Compatible with Angular 17-22
567
+ - Demo project layout improvements are automatic and require no code changes
568
+
569
+ ## [1.9.18] - 2025-11-22
570
+
571
+ ### Fixed
572
+
573
+ - **Mobile Touch Event Handling**: Improved touch listener attachment when calendar opens on mobile devices
574
+ - Touch listeners now properly attach when calendar first opens, eliminating the need to navigate months first
575
+ - Added retry mechanism with multiple attempts to ensure listeners are attached even on slower mobile devices
576
+ - Improved timing with double `requestAnimationFrame` calls and multiple retry strategies
577
+ - Enhanced mobile rendering timing to handle DOM delays
578
+
579
+ ### Changed
580
+
581
+ - **Version Update**: Updated to version 1.9.18
582
+
583
+ ### Migration Notes
584
+
585
+ - This is a patch version update
586
+ - No breaking changes from v1.9.17
587
+ - All changes are backward compatible
588
+ - Compatible with Angular 17-22
589
+ - Improved mobile experience with better touch event handling
590
+
591
+ ## [1.9.17] - 2025-11-21
592
+
593
+ ### Added
594
+
595
+ - **Calendar Button Visibility Control**: Added `showCalendarButton` input property to show/hide the calendar icon button
596
+ - Defaults to `true` for backward compatibility
597
+ - When set to `false`, users can still open the calendar by clicking the input field
598
+ - Useful for custom UI designs or when using `allowTyping` with custom calendar triggers
599
+ - **Calendar Button Styling**: Added `calendarBtn` to `DatepickerClasses` for custom styling of the calendar button
600
+
601
+ ### Changed
602
+
603
+ - **Version Update**: Updated to version 1.9.17
604
+ - **Type Compatibility**: Updated `SignalFormField` type to be fully compatible with Angular 21's `FieldTree<Date, string>` types
605
+
606
+ ### Migration Notes
607
+
608
+ - This is a patch version update
609
+ - No breaking changes from v1.9.16
610
+ - All changes are backward compatible
611
+ - Compatible with Angular 17-22
612
+ - The calendar button is visible by default (`showCalendarButton="true"`), existing behavior unchanged
613
+
614
+ ## [1.9.16] - 2025-11-20
615
+
616
+ ### Fixed
617
+
618
+ - **Range Mode Previous Month Selection**: Fixed issue where users could not select dates from previous months in range mode when starting with `{ start: null, end: null }`
619
+ - Added memo cache invalidation before calendar generation when clicking dates from previous/next months in range mode
620
+ - Fixed issue where clicking dates from previous months would navigate but memoized functions would use stale month/year values
621
+ - Now properly invalidates memo cache in single, range, and multiple modes when navigating to different months via date clicks
622
+ - Users can now select dates from previous months in range mode without issues, allowing proper range selection across month boundaries
623
+
624
+ ### Changed
625
+
626
+ - **Version Update**: Updated to version 1.9.16
627
+ - **Angular 21 Support**: Updated dependencies and peer dependencies to support Angular 21 (officially released)
628
+ - Updated devDependencies to Angular 21.0.0
629
+ - Updated peer dependencies to support Angular 17-22 (`>=17.0.0 <24.0.0`)
630
+ - Full compatibility with Angular 21 including Signal Forms support
631
+ - **Signal Forms**: Full support for Angular 21 Signal Forms with `[field]` input binding (experimental feature)
632
+ - **Zoneless by Default**: Compatible with Angular 21 applications that don't include Zone.js by default
633
+ - **Vitest Compatible**: Works with Angular 21's new default Vitest test runner (library tests use Karma/Jasmine, but library is compatible with Vitest-based apps)
634
+ - **Angular Aria Compatible**: Built-in ARIA support works alongside Angular Aria components (uses custom AriaLiveService for screen reader announcements)
635
+
636
+ ### Migration Notes
637
+
638
+ - This is a patch version update with bug fixes and Angular 21 support
639
+ - No breaking changes from v1.9.15
640
+ - All fixes are backward compatible
641
+ - Compatible with Angular 17-22 (including officially released Angular 21)
642
+
643
+ ## [1.9.15] - 2025-11-20
644
+
645
+ ### Fixed
646
+
647
+ - **Moment Object Binding with ngModel**: Fixed issue where Moment.js objects passed via `[(ngModel)]` were not binding correctly with the datepicker
648
+ - Updated `writeValue()` method to normalize Moment.js objects before passing to `initializeValue()`
649
+ - Ensures Moment.js objects (including those with `utcOffset()` applied) are properly converted to Date objects when binding with template-driven forms
650
+ - Now correctly handles `moment(response.Date).utcOffset(timezone)` when setting via ngModel
651
+ - **Date Clicks After Month Navigation**: Fixed issue where dates became unclickable after navigating backward or forward months
652
+ - Updated `isDateDisabledMemo` getter to properly invalidate cached memoized function when month/year changes
653
+ - Added month/year change detection to ensure disabled date cache is refreshed after navigation
654
+ - Dates in previous/next months are now properly clickable without needing to close and reopen the datepicker
655
+ - **Range Mode Previous Month Selection**: Fixed issue where users could not select dates from previous months in range mode when starting with `{ start: null, end: null }`
656
+ - Added memo cache invalidation before calendar generation when clicking dates from previous/next months in range mode
657
+ - Fixed issue where clicking dates from previous months would navigate but memoized functions would use stale month/year values
658
+ - Now properly invalidates memo cache in single, range, and multiple modes when navigating to different months via date clicks
659
+ - Users can now select dates from previous months in range mode without issues, allowing proper range selection across month boundaries
660
+
661
+ ### Changed
662
+
663
+ - **Version Update**: Updated to version 1.9.15
664
+
665
+ ### Migration Notes
666
+
667
+ - This is a patch version update with bug fixes only
668
+ - No breaking changes from v1.9.14
669
+ - All fixes are backward compatible
670
+ - Compatible with Angular 17 and up versions
671
+
672
+ ## [1.9.14] - 2025-11-20
673
+
674
+ ### Fixed
675
+
676
+ - **Date Picker Selection Issue**: Fixed issue where date picker was not working properly when selecting dates, especially in range mode
677
+ - Added proper change detection scheduling when setting start date in range mode
678
+ - Added memo cache invalidation to ensure UI updates correctly reflect selected dates
679
+ - Fixed UI not updating when only start date is selected in range mode
680
+ - Dates now properly show as selected and calendar updates correctly in all selection modes
681
+ - **Moment.js Timezone Offset Preservation**: Fixed issue where Moment.js objects with timezone offsets (e.g., `moment().utcOffset('-0600')`) were not preserving the timezone offset when converted to Date objects
682
+ - Added `momentToDate()` method that detects and preserves timezone offsets from Moment.js objects
683
+ - Uses moment's `format('YYYY-MM-DDTHH:mm:ss.SSSZ')` to preserve offset information
684
+ - Now correctly handles `moment().utcOffset('-0600')` without requiring `toDate()` which loses timezone information
685
+ - Works for single dates, range values, and array of dates
686
+
687
+ ### Changed
688
+
689
+ - **Version Update**: Updated to version 1.9.14
690
+
691
+ ### Migration Notes
692
+
693
+ - This is a patch version update with bug fixes only
694
+ - No breaking changes from v1.9.13
695
+ - All fixes are backward compatible
696
+
697
+ ## [1.9.13] - 2025-11-19
698
+
699
+ ### Fixed
700
+
701
+ - **valueChange Event Bug**: Fixed issue where `(valueChange)` event was emitting `null` instead of the date value for range mode when using template-driven forms with `[(ngModel)]`
702
+ - Changed `emitValue` method to use `_normalizeValue()` instead of `_normalizeDate()` to properly handle range objects `{ start: Date, end: Date }`
703
+ - Now correctly emits date values for all modes (single, range, multiple)
704
+ - **Range Mode Date Selection**: Fixed issue where dates became disabled/unclickable after navigating to previous or next months in range mode
705
+ - Updated `changeMonth()` method to properly update month/year signals when navigating
706
+ - Fixed `onDateClick()` for all modes (single, range, multiple) to update signals when clicking dates in different months
707
+ - Fixed `onYearClick()`, `onYearSelectChange()`, and `onDecadeClick()` to update signals
708
+ - Ensures memoized `isDateDisabledMemo` function uses correct month/year values after navigation
709
+ - Dates in previous/next months are now properly selectable without needing to close and reopen the datepicker
710
+ - **Moment.js Object Handling**: Fixed issue where Moment.js objects in range values and arrays were not being properly normalized
711
+ - Enhanced `_normalizeValue()` method to explicitly detect and convert Moment.js objects in range objects (`{ start, end }`)
712
+ - Enhanced array value normalization to properly handle Moment.js objects in multiple date selections
713
+ - Ensures Moment.js objects are correctly converted to Date objects before emission in `valueChange` event
714
+
715
+ ### Changed
716
+
717
+ - **Version Update**: Updated to version 1.9.13
718
+
719
+ ### Migration Notes
720
+
721
+ - This is a patch version update with bug fixes only
722
+ - No breaking changes from v1.9.12
723
+ - All fixes are backward compatible
724
+
725
+ ## [1.9.12] - 2025-11-19
726
+
727
+ ### Added
728
+
729
+ - **SEO Optimization**: Comprehensive search engine optimization improvements
730
+ - Enhanced meta tags with expanded keywords, geo-location, and Apple mobile web app tags
731
+ - Complete Open Graph implementation for social media sharing (Facebook, LinkedIn)
732
+ - Enhanced Twitter Card metadata with additional labels and image alt text
733
+ - Multi-locale Open Graph support (en_US, es_ES, fr_FR, de_DE)
734
+ - Structured data (Schema.org) with SoftwareApplication, WebPage, and HowTo schemas
735
+ - robots.txt file with proper crawl directives and sitemap reference
736
+ - sitemap.xml with all important pages, priorities, and change frequencies
737
+ - SEO documentation guide (docs/SEO.md) with best practices and monitoring recommendations
738
+ - **Package Keywords Expansion**: Expanded npm package keywords from 14 to 38 keywords
739
+ - Added keywords for features (signal-forms, SSR, zoneless, accessibility)
740
+ - Added keywords for use cases (date-picker, time-picker, holiday-calendar)
741
+ - Added keywords for qualities (lightweight, customizable, open-source, MIT)
742
+ - Improved discoverability on npm and search engines
743
+ - **README SEO Enhancements**: Added downloads badge and expanded SEO keywords section
744
+ - More comprehensive keyword coverage for better search visibility
745
+ - Enhanced description with additional relevant terms
746
+
747
+ ### Changed
748
+
749
+ - **Version Update**: Updated to version 1.9.12
750
+ - **Multi-Calendar Spacing**: Increased gap between multiple calendars from 16px to 32px for better visual separation
751
+ - Applied to horizontal, vertical, and auto layouts
752
+ - Improved spacing consistency across all multi-calendar configurations
753
+ - **Multi-Calendar Container Sizing**: Enhanced container width handling for multi-calendar layouts
754
+ - Changed from fixed `width: 100%` to `width: fit-content` for better content fitting
755
+ - Increased max-width from 1200px to 1400px to accommodate more calendars
756
+ - Containers now properly expand to fit all calendars without overlapping
757
+ - **Demo App Select Inputs**: Enhanced styling for all select inputs in the demo application
758
+ - Custom dropdown arrow icons with theme-aware colors
759
+ - Improved hover and focus states with smooth transitions
760
+ - Better visual consistency with the overall design system
761
+ - Full dark theme support
762
+ - **Build Configuration**: Updated angular.json to include SEO files in build output
763
+ - robots.txt and sitemap.xml now properly copied to build root
764
+ - Files accessible at site root for search engine crawlers
765
+
766
+ ### Removed
767
+
768
+ - **Demo App Sections**: Removed "2 Calendars Side-by-Side" and "3 Calendars Side-by-Side" demo sections
769
+ - Cleaned up unused TypeScript variables (`multiCalendarRange2`, `multiCalendarSingle3`)
770
+
771
+ ### Fixed
772
+
773
+ - **Multi-Calendar Overlapping**: Fixed issue where multiple calendars would overlap when displayed side-by-side
774
+ - Added proper `box-sizing: border-box` to calendar months
775
+ - Reduced container padding for multi-calendar layouts to provide more space
776
+ - Ensured containers expand to fit content with proper gap spacing
777
+ - **Test Suite**: Fixed TypeScript compilation error in issue-33.spec.ts
778
+ - Fixed undefined `dayNumbers` variable in test assertion
779
+ - Added proper day number collection for debugging when test fails
780
+ - Improved test error messages with actual day numbers found
781
+
782
+ ### Migration Notes
783
+
784
+ - This is a minor version update with backward compatibility
785
+ - No breaking changes from v1.9.11
786
+ - SEO improvements are automatic and require no code changes
787
+ - See [MIGRATION.md](MIGRATION.md) for detailed migration guide
788
+ - See [docs/SEO.md](projects/ngxsmk-datepicker/docs/SEO.md) for SEO best practices
789
+
790
+ ## [1.9.11] - 2025-11-17
791
+
792
+ ### Fixed
793
+
794
+ - **Moment.js Integration with Custom Formats**: Fixed critical issue where Moment.js objects with custom date formats would not populate correctly
795
+ - Added `isMomentObject()` helper method to safely detect Moment.js instances
796
+ - Enhanced `_normalizeValue()` method to handle Moment.js objects directly by extracting native Date using `.toDate()`
797
+ - Improved `parseCustomDateString()` method to use bracket notation for TypeScript compatibility with dynamic object properties
798
+ - Added comprehensive support for format tokens: YYYY, YY, MM, M, DD, D, hh, h, HH, H, mm, m, ss, s, a, A
799
+ - Resolves issue where `moment(this.date).utcOffset(timezone).format('MM/DD/YYYY hh:mm a')` with `displayFormat="MM/DD/YYYY hh:mm a"` would not populate correctly
800
+ - Maintains full backward compatibility with Date objects, strings, and all other supported formats
801
+
802
+ ### Improved
803
+
804
+ - **Custom Format Parser**: Enhanced format token parsing with better TypeScript compatibility
805
+ - **Moment.js Detection**: More robust detection of Moment.js objects across different versions
806
+ - **Demo Application**: Added working Moment.js integration example with interactive controls
807
+
808
+ ## [1.9.10] - 2025-11-15
809
+
810
+ ### Changed
811
+
812
+ - **Version Update**: Updated to version 1.9.10
813
+
814
+ ### Fixed
815
+
816
+ - **Async Database Value Loading**: Enhanced datepicker to properly handle database values that load asynchronously after component initialization
817
+ - Added fallback sync mechanism in `ngAfterViewInit` to catch async database loads
818
+ - Added delayed sync checks in `ngOnInit`, `ngOnChanges`, and `ngAfterViewInit` to handle field value changes that occur after component initialization
819
+ - Added sync on calendar open, focus events, and touch events to ensure values are populated
820
+ - Extended interval sync duration to 30 seconds (from 10 seconds) with 100ms check intervals
821
+ - Ensures datepicker properly displays database values even when they load after the component is rendered
822
+ - **TypeScript Compilation Error**: Fixed `EffectRef` type error when using Angular 17+ `effect()` API
823
+ - Changed `_fieldEffectDestroy: (() => void) | null` to `_fieldEffectRef: EffectRef | null`
824
+ - Updated effect cleanup to use `effectRef.destroy()` instead of function call
825
+ - Added proper `EffectRef` import from `@angular/core`
826
+ - **Test Configuration**: Fixed test configuration for Angular 17+ compatibility
827
+ - Updated karma configuration to work with `@angular/build:karma` builder
828
+ - Simplified karma.conf.js to remove deprecated plugins
829
+ - Updated test script to target correct project
830
+
831
+ ### Improved
832
+
833
+ - **Async Value Handling**: Improved handling of field values that change asynchronously
834
+ - **Effect Management**: Proper effect lifecycle management with `EffectRef` for correct cleanup
835
+ - **Code Cleanup**: Removed unnecessary comments for cleaner codebase
836
+ - **Test Reliability**: Enhanced test configuration for better reliability across Angular versions
837
+
838
+ ## [1.9.9] - 2025-11-15
839
+
840
+ ### Changed
841
+
842
+ - **Version Update**: Updated to version 1.9.9
843
+
844
+ ### Fixed
845
+
846
+ - **Database Value Population**: Fixed critical issue where datepicker would not populate with values from database when using `[field]` input binding
847
+ - Added `_normalizeValue()` helper method to properly handle all value types (Date objects, strings, range objects, arrays)
848
+ - Updated field effect and related methods to use `_normalizeValue()` instead of `_normalizeDate()` which only handled single dates
849
+ - Fixed issue where string dates from database (common scenario) were not being parsed and displayed correctly
850
+ - Now properly handles Date objects, string dates, range objects `{start: Date, end: Date}`, and arrays of dates
851
+
852
+ ### Improved
853
+
854
+ - **Value Normalization**: Improved value normalization to handle all DatepickerValue types consistently
855
+ - **Database Integration**: Enhanced compatibility with database values in various formats (strings, Date objects, etc.)
856
+
857
+ ## [1.9.8] - 2025-11-14
858
+
859
+ ### Changed
860
+
861
+ - **Version Update**: Updated to version 1.9.8
862
+
863
+ ### Fixed
864
+
865
+ - **Date Selection Reset Issue**: Fixed critical bug where selected dates would reset to today's date when using `[field]` input binding
866
+ - Fixed `applyCurrentTime` to create a new Date object instead of mutating the original, preventing reference issues
867
+ - Added `_isUpdatingFromInternal` flag to prevent field effect from resetting the value when updating internally
868
+ - This ensures selected dates are properly stored in the form field instead of being reset to today
869
+
870
+ ### Improved
871
+
872
+ - **Date Mutation Prevention**: Improved date handling to prevent unintended mutations of date objects
873
+ - **Field Update Stability**: Enhanced field binding stability to prevent value resets during internal updates
874
+
875
+ ## [1.9.7] - 2025-11-14
876
+
877
+ ### Changed
878
+
879
+ - **Version Update**: Updated to version 1.9.7
880
+
881
+ ### Fixed
882
+
883
+ - **Calendar Population**: Fixed critical issue where datepicker calendar would not populate with dates when opened, especially when multiple datepickers were present in the same form
884
+ - **Calendar Generation**: Ensured `generateCalendar()` is called when opening the datepicker via click, touch, or programmatic methods
885
+
886
+ ### Improved
887
+
888
+ - **Calendar Initialization**: Improved calendar initialization to ensure dates are always generated before the calendar becomes visible
889
+
890
+ ## [1.9.6] - 2025-11-14
891
+
892
+ ### Changed
893
+
894
+ - **Version Update**: Updated to version 1.9.6
895
+
896
+ ### Fixed
897
+
898
+ - **Multiple Datepicker Management**: Fixed issue where multiple datepickers in the same form would open in the same centered location
899
+ - **Outside Click Detection**: Improved click detection to properly close datepicker when clicking outside the popover and input field
900
+ - **Auto-close Other Datepickers**: When opening a datepicker, all other open datepickers in the same form are now automatically closed
901
+ - **Mobile Datepicker Opening**: Fixed issue where datepicker modal would not open on mobile screens
902
+ - **Datepicker Closing on Mobile**: Fixed issue where datepicker would open and immediately disappear on mobile devices
903
+ - **Select Box Cursor**: Added pointer cursor to all select boxes (month, year, hour, minute, AM/PM) in the datepicker
904
+
905
+ ### Improved
906
+
907
+ - **Document Click Handler**: Enhanced document click handler to check if clicks are inside the popover container, not just the input group
908
+ - **Touch Event Handling**: Improved touch event handling to prevent premature closing on mobile devices
909
+ - **Instance Management**: Added static instance registry to track all datepicker instances for better coordination
910
+
911
+ ## [1.9.5] - 2025-11-14
912
+
913
+ ### Changed
914
+
915
+ - **Version Update**: Updated to version 1.9.5
916
+
917
+ ### Fixed
918
+
919
+ - **Angular 21+ Signal Forms Type Compatibility**: Fixed TypeScript compilation error with Angular 21+ Signal Forms
920
+ - Fixed `Type '() => string' is not assignable to type 'never'` error when using `[field]` input
921
+ - Updated `SignalFormField` type definition to be compatible with Angular 21's `FieldTree<Date, string>` types
922
+ - Maintains backward compatibility with Angular 17-20 where field input is optional
923
+ - Resolves [#33](https://github.com/NGXSMK/ngxsmk-datepicker/issues/33)
924
+
925
+ ## [1.9.4] - 2025-11-14
926
+
927
+ ### Changed
928
+
929
+ - **Version Update**: Updated to version 1.9.4
930
+
931
+ ### Added
932
+
933
+ - **Custom Date Format**: New `[displayFormat]` input property to display dates in custom formats
934
+ - Supports format strings like "MM/DD/YYYY hh:mm A"
935
+ - Works with date adapters (date-fns, dayjs, luxon) or built-in simple formatter
936
+ - Supports common format tokens: YYYY, MM, DD, hh, mm, A, etc.
937
+ - Resolves [#31](https://github.com/NGXSMK/ngxsmk-datepicker/issues/31)
938
+
939
+ ### Fixed
940
+
941
+ - **Time Selection Dropdowns**: Fixed visibility issues with time selection dropdowns
942
+ - Dropdowns now properly display and are not clipped by parent containers
943
+ - Improved z-index handling for time selection dropdowns
944
+ - Removed unnecessary scrollbars from datepicker wrapper
945
+ - Fixed overflow and positioning issues in time selection context
946
+ - Resolves [#32](https://github.com/NGXSMK/ngxsmk-datepicker/issues/32)
947
+ - **Angular 21+ Signal Forms Type Compatibility**: Fixed TypeScript compilation error with Angular 21+ Signal Forms
948
+ - Fixed `Type '() => string' is not assignable to type 'never'` error when using `[field]` input
949
+ - Updated `SignalFormField` type definition to be compatible with Angular 21's `FieldTree<Date, string>` types
950
+ - Maintains backward compatibility with Angular 17-20 where field input is optional
951
+ - Resolves [#33](https://github.com/NGXSMK/ngxsmk-datepicker/issues/33)
952
+
953
+ ## [1.9.3] - 2025-11-13
954
+
955
+ ### Changed
956
+
957
+ - **Version Update**: Updated to version 1.9.3
958
+
959
+ ### Added
960
+
961
+ - **Time-Only Picker**: New `[timeOnly]` input property to display only time selection without calendar
962
+ - Hides calendar grid and shows only time controls (hour, minute, AM/PM)
963
+ - Automatically enables `showTime` when `timeOnly` is true
964
+ - Perfect for time selection scenarios where date is not needed
965
+ - Value is still a Date object using today's date with selected time
966
+ - Placeholder automatically changes to "Select Time" in time-only mode
967
+ - Resolves [#29](https://github.com/NGXSMK/ngxsmk-datepicker/issues/29)
968
+ - **Modern Demo App UI**: Complete redesign of the demo application
969
+ - Modern navbar with glassmorphism effects, search functionality, and improved theme toggle
970
+ - Redesigned sidebar with gradient backgrounds, smooth animations, and visual indicators
971
+ - Enhanced icon sizes and better visual hierarchy
972
+ - Improved responsive design with better mobile experience
973
+ - Automatic system theme detection (dark/light mode preference)
974
+ - Gradient accents, shadows, and modern design patterns throughout
975
+
976
+ ### Fixed
977
+
978
+ - **Test Suite**: Fixed 25+ failing tests across multiple test files
979
+ - **Date Utils Tests**: Fixed `normalizeDate` comparison to use `.toEqual()` instead of `.toBe()` and corrected invalid date handling
980
+ - **Calendar Utils Tests**: Updated `generateMonthOptions` to include required year parameter, fixed `generateTimeOptions` to match new return type (object with `hourOptions`/`minuteOptions`), fixed `generateDecadeGrid` expectations, updated `processDateRanges` to match new return type (object instead of array)
981
+ - **Timezone Utils Tests**: Updated `formatDateWithTimezone` calls to match new signature (locale, options, timezone)
982
+ - **Edge Cases Tests**: Fixed `update12HourState` to check component properties instead of return value, changed `previewEndDate` to `hoveredDate`, fixed date validation and normalization expectations, corrected `applyCurrentTime` to use `currentDisplayHour` and `isPm`, fixed touch event mocks, added change detection for calendar toggle, corrected `isDateDisabled` null handling
983
+ - **Adapters Tests**: Fixed date normalization expectations to match actual behavior
984
+ - **Performance Utils Tests**: Changed array comparison to use `.toEqual()` instead of `.toBe()` for cached results
985
+ - **RTL Tests**: Fixed RTL detection from locale and document direction by properly setting document direction in tests
986
+ - **Touch Gestures Tests**: Fixed swipe handling by creating proper array-like TouchList mock that supports both `item()` and `[0]` indexing
987
+ - **Calendar Views Tests**: Fixed time slider tests to initialize dates and sliders correctly, fixed timeline generation test to call `generateTimeline()` directly
988
+ - **Recurring Dates Utils Tests**: Fixed pattern matching test to use correct date (Jan 6 is Monday, not Jan 8)
989
+ - All 353 tests now pass successfully
990
+
991
+ ## [1.9.2] - 2025-11-12
992
+
993
+ ### Changed
994
+
995
+ - **Bundle Optimization**: Optimized bundle size with improved TypeScript compiler settings
996
+ - Main bundle: ~127KB (source maps excluded from published package)
997
+ - Enhanced tree-shaking with optimized imports and compiler options
998
+ - Added `importsNotUsedAsValues: "remove"` for smaller output
999
+ - Disabled `preserveConstEnums` for better inlining
1000
+ - **Build Process**:
1001
+ - Source maps automatically removed from production builds (saves ~127KB)
1002
+ - Improved build scripts with better error handling
1003
+ - Enhanced bundle analysis that excludes source maps
1004
+ - **Package Configuration**:
1005
+ - Fixed package.json exports to eliminate build warnings
1006
+ - Optimized `files` array to exclude unnecessary files
1007
+ - Updated exports field for better module resolution
1008
+ - **Test Configuration**:
1009
+ - Added Zone.js polyfills to library test configuration
1010
+ - Updated test commands to explicitly target library project
1011
+ - Improved test reliability across Angular versions
1012
+
1013
+ ### Fixed
1014
+
1015
+ - Test suite configuration - added missing Zone.js polyfills for library tests
1016
+ - Bundle analysis now correctly excludes source maps from size calculations
1017
+ - Build warnings from conflicting export conditions resolved
1018
+ - Source map removal script made more resilient for build environments
1019
+
1020
+ ## [1.9.1] - 2025-11-11
1021
+
1022
+ ### Fixed
1023
+
1024
+ - Minor bug fixes and improvements
1025
+
1026
+ ## [1.9.0] - 2025-11-10
1027
+
1028
+ ### Added
1029
+
1030
+ - Extension Points & Hooks system for customization
1031
+ - Enhanced keyboard shortcuts (Y, N, W keys)
1032
+ - Modern UI/UX with improved animations and responsiveness
1033
+ - API documentation with TypeDoc
1034
+ - Semantic release automation
1035
+ - Animation performance optimizations with GPU acceleration
1036
+ - Global search functionality in documentation
1037
+ - Mobile playground for responsive testing
1038
+
1039
+ ### Changed
1040
+
1041
+ - Optimized animations using `transform3d` for hardware acceleration
1042
+ - Reduced animation durations from 0.2s to 0.15s
1043
+ - Improved transition performance with specific property targeting
1044
+ - Updated documentation structure
1045
+ - Enhanced mobile responsiveness
1046
+
1047
+ ### Fixed
1048
+
1049
+ - Animation performance issues
1050
+ - Mobile responsive layout
1051
+ - Sidebar scrollbar styling
1052
+ - TypeScript warnings
1053
+
1054
+ ## [1.8.0] - 2025-11-09
1055
+
1056
+ ### Added
1057
+
1058
+ - Signal Forms support with `[field]` input for Angular 21+
1059
+ - SSR compatibility with platform checks
1060
+ - Zoneless support (works without Zone.js)
1061
+ - Immediate value initialization when `[value]` is set programmatically
1062
+ - Comprehensive documentation for Signals, Signal Forms, and SSR
1063
+ - GitHub Pages deployment automation
1064
+
1065
+ ### Changed
1066
+
1067
+ - Updated peer dependencies to support Angular 17-22 (`>=17.0.0 <24.0.0`)
1068
+ - Added `@angular/forms` as peer dependency
1069
+ - Made `zone.js` optional peer dependency
1070
+ - Enhanced `exports` field in package.json with proper types
1071
+ - Optimized imports for better tree-shaking
1072
+
1073
+ ### Fixed
1074
+
1075
+ - Issue #13: Programmatic value setting now works correctly
1076
+ - SSR compatibility: All browser APIs properly guarded
1077
+ - Value input setter now initializes immediately
1078
+
1079
+ ## [1.7.0] - Previous Release
1080
+
1081
+ _Previous changelog entries..._
1082
+
1083
+ ---
1084
+
1085
+ ## Types of Changes
1086
+
1087
+ - **Added** for new features
1088
+ - **Changed** for changes in existing functionality
1089
+ - **Deprecated** for soon-to-be removed features
1090
+ - **Removed** for now removed features
1091
+ - **Fixed** for any bug fixes
1092
+ - **Security** for vulnerability fixes