Ghost/ghost/admin/app/components/modals/tiers/unarchive.js
Kevin Ansfield 85d7932e45 Resolved deprecation warnings for dynamic modal component binding (#2303)
refs https://github.com/TryGhost/Team/issues/559
refs 054a5f15f5

- with the update of `ember-promise-modals` we started to get deprecation warnings when using `modals.open('modal-component-name')`
  - upcoming Ember build updates will introduce tree shaking but using run-time lookup of modal components by name works against that because it's not statically analysable
- switched to importing components and passing the component class directly, eg. `modals.open(ModalComponent)`
- standardized modal component class names with a `MyModal` style to get better behaviour in code editors when it auto generates imports
- dropped the modal defaults from the modals service because we can now use a static `modalOptions` property on the modal components themselves when we want to override the defaults
2022-03-14 10:52:04 +00:00

32 lines
809 B
JavaScript

import Component from '@glimmer/component';
import {inject as service} from '@ember/service';
import {task} from 'ember-concurrency';
export default class UnarchiveTierModal extends Component {
@service notifications;
@service router;
get isActive() {
const {product} = this.args.data;
return !!product.active;
}
@task({drop: true})
*unarchiveTask() {
const {product, onUnarchive} = this.args.data;
product.active = true;
try {
yield product.save();
onUnarchive?.();
return product;
} catch (error) {
if (error) {
this.notifications.showAPIError(error, {key: 'tier.unarchive.failed'});
}
} finally {
this.args.close();
}
}
}