I discovered a (in my opinion) weird behavior. If I open a dialogService from my plugin I pass a specific part of my $scope.model.value (an array with nested objects in this case) like this:

angular.module("umbraco").controller("myController", function ($scope, dialogService) {

    // Main controller
    $scope.doSomething = function (index) {
        dialogService.open({
            template: '/path/to/template.html',
            show: true,
            modelData: $scope.model.value.array[index],
            callback: function (data) {
                $scope.model.value.array[index] = data;
            }
        });
    };
}

angular.module("umbraco").controller("myDialogController", function ($scope) {

    // Dialog controller
    if ($scope.$parent.dialogOptions.modelData === null || $scope.$parent.dialogOptions.modelData === undefined) {
        $scope.modelData = [];
    } else {
        $scope.modelData = $scope.$parent.dialogOptions.modelData;
    }

     // some method
    $scope.myFunction = function () {

        // create new object
        var item = { prop1: "", prop2: "" };

        // push to array
        $scope.modelData.push(item)

    }
}

• The behavior I would expect is the following:

  I edit some/none/all of the data in my dialog, click submit and then the changed data are given back to my model in the plugin (in this case a new object was added to the array).

• What actually happens:

  I edit some/none/all of the data in my dialog and the plugin model is updated instantly (the object is pushed to my plugin view model as soon as I push it to array in the plugin).

This means for example, if I accidentally delete something in my dialog it can't be undone by just pressing "cancel".

Should I use model.control instead and just "sync" it onSubmit? But if so, how could that be achieved? Or am I missing out some important architectural feature from umbraco/angularjs at this point?