Hey everyone,
This is just a quick post to help out anyone who runs into the same problems with directives that I did today. I was able to call the controllers function from the directive, however none of the parameters were being passed.
The issue ended up being that the parameters need to be named. For instance:
app.directive('ngPlanner', function () {
return {
restrict: 'EA',
templateUrl: '/Businesses/PlannerDirective',
scope: {
lessons: "=",
business: "=",
lessonClicked: "&",
addLesson: "&"
},
replace: true,
link: function (scope, elem, attr) {
var selectedIndex = null;
console.log(scope);
console.log(scope.lessons);
scope.test = function (tester) {
selectedIndex = tester;
console.log("Directive: " + selectedIndex);
scope.lessonClicked({ lesson: selectedIndex });
}
}
}
});
/* Used for handling business details, planner, etc */
app.controller("BusinessDetailsController", function ($scope) {
//Fired when the new lesson button is clicked in the planner directive
$scope.newLesson = function (date) {
console.log("New Lesson Clicked: " + date);
}
//Fired when a lesson is clicked on
$scope.editLesson = function (lesson) {
console.log("Lesson Clicked: " + lesson);
}
});
Note particularly the scope.lessonClicked line. Instead of passing parameters normally, they should be named (scope.lessonClicked({lesson: selectedIndex}).
The naming should match that used in the HTML where your directive is added:
<ng-planner lessons=”plannerLessons” lesson-clicked=”editLesson(lesson)” add-lesson=”newLesson()” business=”true”></ng-planner>
A huge thanks to Jay B for posting the solution on the AngularJS groups page: https://groups.google.com/forum/#!topic/angular/3CHdR_THaNw
He’s also added the following JSFiddle: http://jsfiddle.net/simpulton/VJ94U/
And although pretty well hidden, it is actually mentioned in the documentation: http://docs.angularjs.org/guide/directive
What I Broke - Programming and Web Development 
Leave a Reply to Anonymous Cancel reply