You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
Using angularjs1.2.0-rc.3 the execution of directives based on priority seems reversed.
It is the opposite in previous versions. Is this only for compiling, should I not expect the linking functions to fire in the same order with higher priority first?
Turns out it is related to 31f190d #3558
Was confusing because the default link function is a post link. I would consider this a decent breaking change since it is common to just include a post link function. This change may be necessary for child transclusion but this definitely through me off.
Yeah, there's some info missing. In the commit it's marked as breaking change; not in the changelog though. In migration on the website it's mentioned, but it's not documented in the directive / compile docs.
I'm going to close this since the ordering is working as expected.
I know how frustrating it is to not be able to find this kind of information quickly. If you have any suggestions on improving the way we communicate these changes in the future, I'd love to hear them. Better yet, a PR for the docs would be awesome. :)
Using angularjs1.2.0-rc.3 the execution of directives based on priority seems reversed.
It is the opposite in previous versions. Is this only for compiling, should I not expect the linking functions to fire in the same order with higher priority first?
http://plnkr.co/edit/R1Fd8jxPk5FdR9aC1ke0?p=preview
The text was updated successfully, but these errors were encountered: