Card Deletion in Kanban

Could you please post your onCardDelete implementation?

const modal = await DayPilot.Modal.confirm("Delete this Task?");
if (modal.canceled) {
  return;
}

At this moment, onCardDelete doesn’t support asynchronous processing. With the current version, you would have to use the built-in confirm() dialog which is synchronous:

onCardDelete: args => {
    const result = confirm("Delete this Task?");
    if (!result) {
        args.preventDefault();
    }
}

I’ve added the async handling to the wishlist, so in the future you will be able to use something like this:

onCardDelete: async args => {
  args.async = true;
  const modal = await DayPilot.Modal.confirm("Delete this Task?");
  if (modal.canceled) {
    args.preventDefault();
  }
  args.loaded();
}

Is there anyway for us to get control of the deletion process so that we can do some other tasks or do we have to use the process as shown above?

At this moment, no.

Soon, the Kanban component will support an onBeforeCardRender event which will let you add custom icons using active areas. You can define a custom click event handler for active areas where you can implement your own logic.

This will allow defining a custom delete button (your icon at the specified position, with your own onClick handler).

Actually, you don’t need the async support to make this work. You just need to switch the logic: Cancel the default action first and delete the event manually if the user confirms the action:

onCardDelete: async args => {
  args.preventDefault();
  const modal = await DayPilot.Modal.confirm("Delete this Task?");
  if (modal.canceled) {
    return;
  }
  kanban.cards.remove(args.card);
}

Great.

If you delete a card via the context menu or the delete button you get 2 different arguments.

One has a source and the other has a crad property.

It would be nice if both returned the same so that we don’t have to check this in code. (maybe!)

The context menu is universal and it receives different source objects, depending on the source element. So unfortunately it has to stay this way.