-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Each iterator on the repeated DOM element instead of container #23
Comments
Can you post a code example? I think I know what you mean, just want to check |
I first noticed this when trying to run the following:
|
Mainly because it causes weird complications with having to worry about the order bindings are processed. That leads to a whole lot of weird mess that can usually be avoided by modifying the markup a little bit. It could work if there was a limitation that you couldn't use other directives on the same element if you're using |
Sure, thanks for the clarification. As I've said, it was more curiosity than anything and indeed im more interested in explore how to control that kind of stuff with directives. |
Following the iteration example, i've noticed that the directive is passed in the container element instead of the element being cloned at each loop.
This might present some limitations, one example being the following.
Let's say I have a
ul
that contains my data items. When there are no items to show I wan't to show anli
with some specific formatting. If I try that now, just by having the extrali
inside the element whereeach
is applied it breaks.This is more a question than a suggestion, just curious about the reasons behind that design option.
The text was updated successfully, but these errors were encountered: