fa84808048
no issue Since `ember-moment@10.0` it's not been necessary to use the `ember-cli-moment-shim` package, with `moment` instead being usable directly via `ember-auto-import`. Getting rid of the shim package is necessary for compatibility with `embroider`, Ember's new build tooling. - dropped `ember-cli-moment-shim` dependency - added `moment-timezone` dependency and updated all imports to reflect the different package - worked around `ember-power-calendar` having `ember-cli-moment-shim` as a sub-dependency - added empty in-repo-addon `ember-power-calendar-moment` to avoid `ember-power-calendar` complaining about a missing package - added `ember-power-calendar-utils` in-repo-addon that is a copy of `ember-power-calendar-moment` but without the build-time renaming of the tree for better compatibility with embroider
20 lines
549 B
JavaScript
20 lines
549 B
JavaScript
import moment from 'moment-timezone';
|
|
import {helper} from '@ember/component/helper';
|
|
|
|
export function mostRecentlyUpdated(objs) {
|
|
const items = [...(objs || [])];
|
|
|
|
(items || []).sort((a, b) => {
|
|
const momentA = moment(a.updatedAtUTC || a.updatedAt || a.updated_at);
|
|
const momentB = moment(b.updatedAtUTC || b.updatedAt || b.updated_at);
|
|
|
|
return momentB.valueOf() - momentA.valueOf();
|
|
});
|
|
|
|
return items[0] || null;
|
|
}
|
|
|
|
export default helper(function ([items = []]) {
|
|
return mostRecentlyUpdated(items);
|
|
});
|