From ba9314593cfa0719045a9499657df7c630d72a8c Mon Sep 17 00:00:00 2001 From: malayaleecoder Date: Wed, 1 Jun 2016 15:54:30 +0530 Subject: [PATCH] Fix Friendly Date Range issue --- .../advanced-bonfires.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/challenges/01-front-end-development-certification/advanced-bonfires.json b/challenges/01-front-end-development-certification/advanced-bonfires.json index f3cb326de9..d4dfdf0928 100644 --- a/challenges/01-front-end-development-certification/advanced-bonfires.json +++ b/challenges/01-front-end-development-certification/advanced-bonfires.json @@ -269,7 +269,7 @@ "Convert a date range consisting of two dates formatted as YYYY-MM-DD into a more readable format.", "The friendly display should use month names instead of numbers and ordinal dates instead of cardinal (1st instead of 1).", "Do not display information that is redundant or that can be inferred by the user: if the date range ends in less than a year from when it begins, do not display the ending year.", - "Additionally, if the date range begins in the current year and ends within one year, the year should not be displayed at the beginning of the friendly range.", + "Additionally, if the date range begins in the current year (i.e. it is currently the year 2016) and ends within one year, the year should not be displayed at the beginning of the friendly range.", "If the range ends in the same month that it begins, do not display the ending year or month.", "Examples:", "makeFriendlyDates([\"2016-07-01\", \"2016-07-04\"]) should return [\"July 1st\",\"4th\"]",