zachsnow

@Kidlike what would be the best approach? (Don't use bower etc.)

@iconico sorry, I meant how should it be included in the package to be useful?

Yup!

Hey there, this is essentially related to a known issue with multi-transclusion as implemented by this library (trying to hook into "native" AngularJS transclusion). With no good fix in mind...

Thanks for the report. I think this would be technically working "as intended" as the names of the multi-transclusion wouldn't be available in the `my-custom-directive` body. However, as noted this...

That was indeed added to address a memory leak, however it was not one that I witnessed. In any event it seems like it would be nice to use `$animate`...

@defualt I believe that the (possible) need for that code has been obviated by the most recent commit, whereby all DOM nodes remain attached to the document. I'll try to...

The current approach that `ng-multi-transclude` takes to linking content does not afford a way to relink individual blocks, nor does it correctly relink when a block is removed and then...

This should be straightforward so long as we never allow dynamic template names nor block names.

Thanks for the report I'll check it out.