I understand what you intend in this PR (#111).
I feel it is too complex, and it is not efficient both callbacks, an original callback and a callback from attributes, are invoked in every callback.
So, I fixed such as https://gist.github.com/outsideris/4045c5912d116511d3b2. How do you think about that?
I wanted it use basically callbacks in summernote config object and overwrite it if a user specifies callback in an attribute.

That would work, as long as you still make a copy of the original config object (I can't see it in the gist you made):

var currentElement, summernoteConfig = angular.copy($scope.summernoteConfig) || {};

@shadybones I make the diff in gist on top of your commit so, I ommit the making a copy parts.
If you agreed with the diff, please update your PR. After that I will merge it.
Let me know if you are busy. I will modify it after I merge your current PR.

@outsideris I'm wondering, was there a reason onChange was done differently than the rest of the callbacks? I've implemented your changes into the PR.

Thank you.
onChange is defferent because it have to sync with ngModel.