Forms signal minDate and maxDate validator#67544
Forms signal minDate and maxDate validator#67544brunoredes wants to merge 1 commit intoangular:mainfrom
Conversation
Add dedicated `minDate()` and `maxDate()` validation rules for string-based date and time form fields. These validators use lexicographic string comparison, which correctly handles ISO-formatted values from `<input type="date">`, `<input type="time">`, and `<input type="datetime-local">`. Both validators support static string values, dynamic values via LogicFn, and custom error messages/functions.
JeanMeche
left a comment
There was a problem hiding this comment.
Looks like this implementation is incomplete (or at least not covered by tests).
Check out packages/forms/signals/test/web/form_field_directive.spec.ts, you'll see that min/minlength etc add the matching attribute to the dom.
@JeanMeche it seems I will change some code from |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The min() and max() validators only accept numeric values as the constraint argument. When used with string paths, passing a string like '2025-06-01' results in a TypeScript error.
This prevents using these validators for date/time inputs without workarounds.
Issue Number: 151664003
What is the new behavior?
minDate()validator that validates string-based form fields (date, time, datetime-local) are greater than or equal to a given minimum string value using lexicographic comparison.maxDate()validator that validates string-based form fields (date, time, datetime-local) are less than or equal to a given maximum string value using lexicographic comparison.min()andmax().Does this PR introduce a breaking change?
Other information
Solves Experimental Signal Forms (view)