fix(timeline): validate RANGE end-date client-side with a field-level error
A RANGE event with a blank end date passed validateEventForm and reached the backend, which 400s with a generic INVALID_DATE_RANGE mapped to "end must not be before start" — wrong for a missing end date, and shown only as a top-of-form alert. Validate it before the API call and surface a dedicated event_editor_end_date_required message on the end-date field via a new DatePrecisionField endDateError prop (defaults '', so the document form is unchanged). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -1056,6 +1056,7 @@
|
||||
"event_editor_title_placeholder": "Event title",
|
||||
"event_editor_title_required": "Please enter a title.",
|
||||
"event_editor_date_required": "Please enter a date.",
|
||||
"event_editor_end_date_required": "Please enter an end date.",
|
||||
"event_editor_type_label": "Type",
|
||||
"event_editor_persons_label": "People",
|
||||
"event_editor_documents_label": "Letters",
|
||||
|
||||
Reference in New Issue
Block a user