{"action":"closed","issue":{"url":"https://api.github.com/repos/wildlyinaccurate/angular-relative-date/issues/12","repository_url":"https://api.github.com/repos/wildlyinaccurate/angular-relative-date","labels_url":"https://api.github.com/repos/wildlyinaccurate/angular-relative-date/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/wildlyinaccurate/angular-relative-date/issues/12/comments","events_url":"https://api.github.com/repos/wildlyinaccurate/angular-relative-date/issues/12/events","html_url":"https://github.com/wildlyinaccurate/angular-relative-date/issues/12","id":81362707,"number":12,"title":"Date that already includes daylight saving is compared incorrectly","user":{"login":"vivaladan","id":1514212,"avatar_url":"https://avatars.githubusercontent.com/u/1514212?v=3","gravatar_id":"","url":"https://api.github.com/users/vivaladan","html_url":"https://github.com/vivaladan","followers_url":"https://api.github.com/users/vivaladan/followers","following_url":"https://api.github.com/users/vivaladan/following{/other_user}","gists_url":"https://api.github.com/users/vivaladan/gists{/gist_id}","starred_url":"https://api.github.com/users/vivaladan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vivaladan/subscriptions","organizations_url":"https://api.github.com/users/vivaladan/orgs","repos_url":"https://api.github.com/users/vivaladan/repos","events_url":"https://api.github.com/users/vivaladan/events{/privacy}","received_events_url":"https://api.github.com/users/vivaladan/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2015-05-27T09:17:08Z","updated_at":"2016-10-28T08:57:12Z","closed_at":"2016-10-28T08:57:12Z","body":"The date string I'm using the filter upon is already correct with respect to daylight saving changes. This is because the API that it comes from is returning local time, in this case GMT+1.\r\n\r\nUsing this string as a parameter to the js date obj inside the filter, applies +1 again. This means that the calculated relative time is out by an hour having had DST corrected twice.\r\n\r\n\r\n---\r\nAs I can't change the web-server to return UTC without DST, I've used moment.js and it's relative time function inside my own angular filter."}}
{"actor":{"display_login":"wildlyinaccurate"}}