From 6e051fb65e2c1d1583ff16a6523b0d5282ff4729 Mon Sep 17 00:00:00 2001 From: webnoob Date: Thu, 8 Nov 2018 23:07:42 +0000 Subject: [PATCH] Clarify formatDate i18n usage Update to add clarity to how formatDate handles i18n. The third parameter only needs to be used when using your own custom i18n instance. Quasar will handle it's own internal one and set the locale when it changes. --- source/components/date-utils.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/components/date-utils.md b/source/components/date-utils.md index efae7ab7..a8235b61 100644 --- a/source/components/date-utils.md +++ b/source/components/date-utils.md @@ -32,7 +32,7 @@ let timeStamp = Date.now() let formattedString = date.formatDate(timeStamp, 'YYYY-MM-DDTHH:mm:ss.SSSZ') ``` -For i18n, you can use a third parameter: +For `$q.i18n` (Quasar's built in localization), locale will be set automatically based on the global quasar `locale`. For custom i18n, you can use a third parameter: ```js let formattedString = date.formatDate(timesStamp, 'MMMM - dddd', { dayNames: ['Duminica', 'Luni', /* and all the rest of days - remember starting with Sunday */],