index.js (2)

65-67: Consider adding validation for more robust year-only detection.

The split('-').length !== 1 check works well for properly formatted ISO dates, but could be more explicit. For example, a malformed input like "2022-" would be treated as a full date but might produce unexpected results.

For increased clarity and robustness, consider an explicit regex check:

-  const localeString = body.split('-').length !== 1
-    ? date.toLocaleDateString(DATE_LOCALE, LONG_DATE_FORMAT)
-    : date.toLocaleDateString(DATE_LOCALE, SHORT_DATE_FORMAT);
+  const isYearOnly = /^\d{4}$/.test(body);
+  const localeString = isYearOnly
+    ? date.toLocaleDateString(DATE_LOCALE, SHORT_DATE_FORMAT)
+    : date.toLocaleDateString(DATE_LOCALE, LONG_DATE_FORMAT);

---

63-64: Add error handling for invalid dates in the date helper.

The Handlebars date helper at lines 58-67 lacks validation for date input. While the falsy check at line 59 handles missing dates, it doesn't catch invalid date strings (e.g., "invalid" or "2024-13-45"). Calling toISOString() on an Invalid Date object throws a RangeError. Add a validation check before line 64, such as:

if (Number.isNaN(date.getTime())) {
  return body; // or handle error appropriately
}

This provides defensive error handling against malformed date input that bypasses the schema.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro