subdigital
Explain YYYY vs yyyy
Some tweets went around recently noting how YYYY might not be what you want to be using, but rather yyyy or y. The "references" omits YYYY and how it differs from its lowercased counterparts.
Has there been any progress on this? Our team recently encountered this issue. We got the "week year" instead of the desired "day year" in our formatted date string. Since your site is a respected reference for the date formatter, it would be really helpful if you highlight this subtle (for instance it doesn't make a difference every year like 2022) for developers that are not as versed in the nuances of the ISO date standard.
Nothing was changed here, no. The references section omits the YYYY variant to avoid confusion. If you want to add a blurb to the Best Practices section (or a references row with a strong disclaimer) feel free to send me a PR :)
Ben,
Will do. Thank you for the quick response.
David
On Fri, Dec 10, 2021 at 1:57 PM Ben Scheirman @.***> wrote:
Nothing was changed here, no. The references section omits the YYYY variant to avoid confusion. If you want to add a blurb to the Best Practices section (or a references row with a strong disclaimer) feel free to send me a PR :)
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/subdigital/nsdateformatter.com/issues/31#issuecomment-991254526, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASI6BOG4Z7B7NCQKDCYPRLUQJLR5ANCNFSM4VPTSDDA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.