{"action":"created","issue":{"url":"https://api.github.com/repos/djhi/meteor-autoform-materialize/issues/102","repository_url":"https://api.github.com/repos/djhi/meteor-autoform-materialize","labels_url":"https://api.github.com/repos/djhi/meteor-autoform-materialize/issues/102/labels{/name}","comments_url":"https://api.github.com/repos/djhi/meteor-autoform-materialize/issues/102/comments","events_url":"https://api.github.com/repos/djhi/meteor-autoform-materialize/issues/102/events","html_url":"https://github.com/djhi/meteor-autoform-materialize/issues/102","id":166889751,"number":102,"title":"pickadate is not persisting the date object in the desired timezone?","user":{"login":"keyscores","id":1364012,"avatar_url":"https://avatars.githubusercontent.com/u/1364012?v=3","gravatar_id":"","url":"https://api.github.com/users/keyscores","html_url":"https://github.com/keyscores","followers_url":"https://api.github.com/users/keyscores/followers","following_url":"https://api.github.com/users/keyscores/following{/other_user}","gists_url":"https://api.github.com/users/keyscores/gists{/gist_id}","starred_url":"https://api.github.com/users/keyscores/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/keyscores/subscriptions","organizations_url":"https://api.github.com/users/keyscores/orgs","repos_url":"https://api.github.com/users/keyscores/repos","events_url":"https://api.github.com/users/keyscores/events{/privacy}","received_events_url":"https://api.github.com/users/keyscores/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-07-21T18:43:09Z","updated_at":"2016-07-23T15:42:07Z","closed_at":null,"body":"I would expect that the date persisted to db would also be converted to timezoneID specified. Or is it just for displaying the timezone?\r\n\r\nIf one specifies a schema with:\r\n\r\n```\r\n  pickadateTimezone: {\r\n    type: Date,\r\n    optional: true,\r\n    autoform: {\r\n      type:\"pickadate\",\r\n      timezoneId: \"America/Los_Angeles\"\r\n    }\r\n  },\r\n```\r\n\r\nI would expect the date in the DB to be offset to Los Angeles time, instead I get the browser time.\r\n\r\nsee reproduction here: \r\nhttps://github.com/keyscores/autoform_materialize_date_timzeone_issue\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/djhi/meteor-autoform-materialize/issues/comments/234724738","html_url":"https://github.com/djhi/meteor-autoform-materialize/issues/102#issuecomment-234724738","issue_url":"https://api.github.com/repos/djhi/meteor-autoform-materialize/issues/102","id":234724738,"user":{"login":"serkandurusoy","id":4649948,"avatar_url":"https://avatars.githubusercontent.com/u/4649948?v=3","gravatar_id":"","url":"https://api.github.com/users/serkandurusoy","html_url":"https://github.com/serkandurusoy","followers_url":"https://api.github.com/users/serkandurusoy/followers","following_url":"https://api.github.com/users/serkandurusoy/following{/other_user}","gists_url":"https://api.github.com/users/serkandurusoy/gists{/gist_id}","starred_url":"https://api.github.com/users/serkandurusoy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/serkandurusoy/subscriptions","organizations_url":"https://api.github.com/users/serkandurusoy/orgs","repos_url":"https://api.github.com/users/serkandurusoy/repos","events_url":"https://api.github.com/users/serkandurusoy/events{/privacy}","received_events_url":"https://api.github.com/users/serkandurusoy/received_events","type":"User","site_admin":false},"created_at":"2016-07-23T15:42:07Z","updated_at":"2016-07-23T15:42:07Z","body":"Well, this component has been out and in use for more than a year and I am sure there are a lot of people who either consciously or unconsciousl relying on how it handles dates. So changing it would probably come at a big surprize and even damaging for some people.\r\n\r\nI believe the way to fix this is not to change this component but either one of:\r\n\r\n* add a new property such as `convertToCustomTimezone` that opts in to a different behavior\r\n* create a new component that is simply based on this one but does what you want (it should be very easy to do this and in fact you can do it now as a local package in your app)\r\n"}}
{"actor":{"display_login":"serkandurusoy"}}