ngxsmk-datepicker 2.1.3 → 2.1.4

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