What is the correct way to pass a controller function to a second level directive in AngularJS?

Question

JavaScript

There is the following markup:

<div ng-controller="ClientsCtrl">
    <table-panel data="data" action-delete="client_delete(id)">
        ...
        <data-table rows="rows" action-delete="???">
            ...
            <table>
                <tbody>
                    <tr ng-repeat="row in rows">
                        <td>
                            <a ng-click="entity_delete(row.id)">Delete</a>
                        </td>
                    </tr>
                </tbody>
            </table>
            ...
        </data-table>
        ...
    </table-panel>
</div>

where, table-panel and data-table are directives.
Those. there is a page with a panel, in the panel there is a table with data, the row has a delete button. The table and the panel are made by directives so that they can be used on different pages, for different data.
What should happen when the delete button is clicked is described in the ClientsCtrl controller.
Directive code:

controls.directive('tablePanel', function () {
    return {
        restrict: 'E',
        scope: {
           actionDelete: '&'
        }
    }
});

controls.directive('dataTable', function(){
    return {
        restrict: 'E',
        scope:{
            actionDelete: '&'
        },
        controller: function($scope){
            $scope.entity_delete = function (id) {
                $scope.actionDelete({id: id});
            };
        }
    };
});

What should be written in the markup on the line <data-table rows="rows" action-delete="???">in the action-delete attribute?
If we write actionDelete(id), we will get an error when the button is clicked:
Cannot use 'in' operator to search for 'client_delete' in 1
If I understand correctly, we can create a method in the controller of the tablePanel directive and link to it already.
The question is, is it possible to do without creating a method that will simply pull another method?

Answer 1

From simple options: use the controller definition in the notation ng-controller="Controller as controllerName", and call the controller method directly.