{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"closed","user":{"avatar_url":"https://secure.gravatar.com/avatar/2a8d0ffd6cd04bee1add0e3554013c90?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"2a8d0ffd6cd04bee1add0e3554013c90","url":"https://api.github.com/users/kuon","login":"kuon","id":160200},"milestone":null,"labels":[],"assignee":null,"updated_at":"2011-11-13T08:59:01Z","closed_at":"2011-11-12T21:53:16Z","comments":2,"url":"https://api.github.com/repos/csnover/js-iso8601/issues/3","body":"The following date doesn't parse:  \"10000-01-31T23:00:00Z\"\r\n\r\nWe are using this date as \"distantFuture\" in our applications.\r\n\r\nI patched the regex by replacing `\\d{4}` with `\\d{4,5}`, but in the standard, it is said that it is limited to 4 digits except if there is mutual agreement.\r\n\r\nRuby on rails generates the above string for year 10000.\r\n\r\n\r\n","html_url":"https://github.com/csnover/js-iso8601/issues/3","title":"Year 10 000 does not parse.","number":3,"id":1811247,"created_at":"2011-10-04T08:11:45Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/2a8d0ffd6cd04bee1add0e3554013c90?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"2a8d0ffd6cd04bee1add0e3554013c90","url":"https://api.github.com/users/kuon","login":"kuon","id":160200},"updated_at":"2011-11-13T08:59:01Z","url":"https://api.github.com/repos/csnover/js-iso8601/issues/comments/2721399","body":"Yea you are right, I didn't realise that while busy on my project.\r\n\r\nPlease disregard this issue then.\r\n\r\nSent from my iPhone\r\n\r\nOn 12 nov. 2011, at 22:53, Colin Snover<reply@reply.github.com> wrote:\r\n\r\n> Ruby on Rails is generating invalid date strings that this library will not handle. Without hyphens (which are optional) the year-month format would be ambiguous versus the year-day format and allowing this format would bloat the library significantly. ISO 8601 specifies that expanded representations must be prefixed with ± (ISO 8601:2004(E) §4.1.2.4). Please contact RoR and tell them to fix their date functions.\r\n> \r\n> --- \r\n> Reply to this email directly or view it on GitHub:\r\n> https://github.com/csnover/js-iso8601/issues/3#issuecomment-2719592","id":2721399,"created_at":"2011-11-13T08:59:01Z"}}