@masterteam/task-schedule 0.0.21 → 0.0.22

package/fesm2022/masterteam-task-schedule.mjs

@@ -3721,6 +3721,16 @@ class TaskSchedule {
             this.openScheduleDialog(args?.requestType === 'beforeOpenEditDialog' ? 'edit' : 'create', args);
             return;
         }
+        // Context-menu "Add > Above/Below/Child" calls Gantt's addRecord directly,
+        // so it never raises beforeOpenAddDialog — the row is inserted locally and
+        // never persisted (it vanishes on refresh). Cancel that local-only add and
+        // route it through the create dialog, which saves it with the correct
+        // parent (parentGuid is resolved from the right-clicked anchor row).
+        if (args?.requestType === 'beforeAdd' && this.isContextAddAction()) {
+            args.cancel = true;
+            this.openScheduleDialog('create', args);
+            return;
+        }
         if (args?.requestType === 'beforeDelete') {
             args.cancel = true;
             const taskId = this.actionService.readDeleteTaskId(args);
@@ -4013,12 +4023,18 @@ class TaskSchedule {
     }
     resolveParentGuidForContextAddTask(task) {
         const actionId = this.contextAddTask();
+        // The anchor is Syncfusion's row object, which keeps the original record
+        // (and its custom guid/parentGuid) under `taskData` rather than at the top
+        // level. Fall back to it so the subtask is actually created with a parent.
+        const taskData = task?.['taskData'];
+        const guid = task?.guid ?? taskData?.guid;
+        const parentGuid = task?.parentGuid ?? taskData?.parentGuid;
         if (actionId.endsWith('_contextMenu_Child')) {
-            return String(task?.guid ?? '');
+            return String(guid ?? '');
         }
         if (actionId.endsWith('_contextMenu_Below') ||
             actionId.endsWith('_contextMenu_Above')) {
-            return String(task?.parentGuid ?? '');
+            return String(parentGuid ?? '');
         }
         return null;
     }