Moment.js amDateFormat 总是返回 1970 年的日期

<td class="timespan">{{tag. added_epoch |amDateFormat:'dddd, MMMM Do YYYY'}}</td>

这就是 tag.added_epoch 值是 added_epoch: 1432252800

但是当我在线转换时，我得到了正确的日期:

知道为什么我的过滤器会将 1432252800 变成 Saturday, January 17th 1970?

解决方案

我只是快速总结问题和解决方案.

Moment.js 提供了两种不同的方法来根据 unix 时间戳创建日期moment(1432252800) 和 moment.unix(1432252800).

两者同时开始(1970 年 1 月 1 日凌晨 12 点 UTC)，但 moment() 使用以毫秒为单位的数字，大约是 17 天和 moment.unix() 使用秒数.

angular-moment 支持 amFromUnix 过滤器，参见 来源

你可以通过以下方式使用它

<time am-time-ago="myDate|amFromUnix">{{myDate|amFromUnix|amCalendar}}

http://plnkr.co/edit/5zxXEEz30t51yGhgYWVF?p=preview

I'm using Moment.js and Angular-moment in my app.

For some reason it's converting all my epoch timestamps to the same date from 1970.

<td class="timespan">{{tag.added_epoch | amDateFormat:'dddd, MMMM Do YYYY'}}</td>

This is what the tag.added_epoch value is added_epoch: 1432252800

However when I convert it online, I get the correct date:

Any idea why my filter is turning 1432252800 into Saturday, January 17th 1970?

解决方案

I'm just quickly summarizing the problem and solution.

Moment.js offers two different ways to create a date from a unix timestamp moment(1432252800) and moment.unix(1432252800).

Both start at the same time (Jan 1 1970 12AM UTC) but moment() uses the number as milliseconds, which are around 17 days and moment.unix() uses seconds.

angular-moment supports the amFromUnix filter, see source

You can use it the following way

<time am-time-ago="myDate|amFromUnix">
{{myDate|amFromUnix|amCalendar}}