Mmyeah.. isolated scopes are kind of an 'expected' thing.  I guess let's just go with them.



On May 9, 2013 at 8:54:47 AM, Pawel Kozlowski (notifications@github.com) wrote:
In src/alert/alert.js:
>      link: function(scope, iElement, iAttrs, controller) {
> -      scope.closeable = "close" in iAttrs;
> +
> +      var isClosable = 'close' in iAttrs;
> +      var closeFn = isClosable ? $parse(iAttrs.close) : angular.noop;
> +
> +      scope.type = $parse(iAttrs.type)(scope);
> +      scope.closeable = isClosable;
> +
> +      scope.close = function() {
@ajoslin you are right... Oh, dear, so isolated scope indeed makes sense... Even if we add a child scope here (scope: true) it will make the situation a bit better, as we won't override any methods and people will be able to do $parent.close().
But give all this I wonder if we should merge this at all... Isolated scopes are introducing some pitfalls but have their benefits as well...
— Reply to this email directly or view it on GitHub.￼