Jeremy Mickelson

Sounds good, but `preprocessDate` doesn't seem to do that. Here's it's full code: ``` js this.preprocessDate = function (value) { // Configure the default timezone if needed if (defaultTimezone !==...

I can sure try. Let's see what I can come up with.

Here's a failing test. It passes on 0.10.3 ``` js it('should apply the configured timezone to moment objects', function () { angularMomentConfig.timezone = 'Pacific/Tahiti'; var timestamp = moment.tz('2012-01-22T12:46:54Z', 'UTC'); expect(amDateFormat(timestamp,...

I'm not sure I have the background to do so. In 0.10.3, there is the `applyTimezone` function that is used all over the place. In 1.0.0 it has been removed....

Ahh, see that's not that simple for me either. All of my dates come down from the server in UTC so are parsed in moment as having a UTC timezone....

Not a bad idea. I'm signing off of work for today, so I'll check on this tomorrow. It might be the right thing for my project. You still might want...

I agree that splitting things up into multiple compossible filters made the project less complicated and more approachable, but it does seem like we've lost some important functionality here. It...

Not really. I had to use the preprocess function suggested by @urish, so I'm hard coded to one timezone per browser instance.

I have the same problem as @gasi. I have the following wrapping function ``` coffee ScheduleController = ($scope, $window, gToast, Schedule, AppointmentResource, AppointmentType, Employee, user) -> Schedule.get(practiceId: user.practiceId, { editing:...

@kolobock, I would love to see this feature added to typedstore, would it be difficult to improve it so the tests pass?