Error when yield-to is null about mobile-angular-ui HOT 2 CLOSED

yieldTo content is saved as a string in a variable and re-appended to its container as default each time a route changes thus it is compiled with $compile just like the contentFor content.

So the same would happen with an empty contentFor.

Now the problem is that $compile implicitly passes strings to angular.element in order to convert it to a new dom element. If the string doesn't start with an html tag it assumes that is an attempt to use a jquery selector thus raising an error for the unsupported feature.

This is the code where the issue happens:

setContentFor: (name, content, scope) ->
    b = yielders[name]
    return unless b
    sanitizedContent = content.replace(/^\s+/, "")
    compiled = $compile( sanitizedContent )(scope)
    b.element.empty().append(compiled)

A quick fix could be to check if sanitizedContent is empty and just empty yield-to accordingly. But it would not work with another string. The following would also raise an error:

 <div class="navbar-brand navbar-brand-center" yield-to="title">
   The title
 </div>

So for now you can include an empty span if its not a problem.

 <div class="navbar-brand navbar-brand-center" yield-to="title">
   <span></span>
 </div>

I wish to figure out a better and more generic workaround, do you know a better way to overcome this problem?

from mobile-angular-ui.

Ok I found the right way to do that in the ngInclude source:

    b.element.html(content)
    $compile(b.element.contents())(scope)

Just released 1.0.7-beta fixing this issue.

Thank you

from mobile-angular-ui.