Pete Browne
Pete Browne
+1 for the original feature request. The trick @Fresheyeball suggested is cool, but I don't like having to modify other libraries just to use CoffeeScript.
Yeah a PR would be appreciated!
If you have the time, I'll gladly look over and help with a PR to add support for sassc!
Yeah I get `2014-11-21T04:30:00-06:00` now, very odd...could DST changes affect this as well? Just to clarify: I'm not using `_isUTC`, I just noticed the flag was different while debugging
I still get inconsistent results with `0` instead of `'UTC'` ``` javascript var m1 = moment('2014-11-21T10:30:00-06:00'); m1.utcOffset(0, true).format(); // "2014-11-21T10:30:00+00:00" var m2 = moment.tz('2014-11-21T10:30:00', 'America/Chicago'); m2.utcOffset(0, true).format(); // "2014-11-21T04:30:00-06:00" ```
I'm receiving a datetime from an API in UTC and converting it to a user's timezone for display. That seems like a pretty valid use-case?
The problem I have is that I can't guarantee the original timestamp is UTC, which is why I'm initializing with `moment.tz` instead of `moment.utc`
Is there any documentation for the `populator` option? This is still empty: http://trailblazer.to/gems/representable/3.0/populator.html What's the equivalent for `parse_strategy: :find_or_initialize`?
Would you be interested in working on this and submitting a PR?
I'm not able to reproduce this, what does your route function look like?