directive-start, directive-end syntax is incompatible with ngController.

[sukei]

The current implementation doesn't allow the usage of directive-start, directive-end syntax with ngController directive.

Here is a plunkr that shows the issue: http://plnkr.co/edit/gWdNsc?p=preview

[caitp]

That's kind of interesting. I'm not sure if ngController is meant to be used with the -start/-end scheme (which, if my patch lands, will be much more restricted in the future) --- but it is interesting that it only gets applied to the element it's instantiated on, and not all of the collected elements for the directive. I guess the reason for this lives in the controller instantiating stuff here, which only gets applied to the element, and not shared by the collected elements.

Sort of unexpected in comparison with the -start and -end stuff, but as I said, I am hoping -start and -end will be restricted a lot more in the future so that it's clear what the desirable behaviour is.

[gsklee]

@caitp Can we have a link to the patch you've mentioned?

I think there should be a flag in directive config object that toggle the range apply behavior on/off. This was originally only meant for ngRepeat; making it freely available is like making it free-for-all. This is bound to cause unexpected issues.

[rodyhaddad]

@gsklee #5372 for caitp's patch, needs more +1s :-)

[btford]

@sukei do you have a use case for this in mind?

If so, post it below and I'll reopen this for further discussion. Otherwise, I think @caitp's fix looks good.