Skip to content
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

Bug on Directives #2756

Closed
l-Leniac-l opened this issue Jun 27, 2015 · 3 comments
Closed

Bug on Directives #2756

l-Leniac-l opened this issue Jun 27, 2015 · 3 comments

Comments

@l-Leniac-l
Copy link

Hello!
On directives I have detected the following problem:

If you include coreDirectives and NgFor in the same component, the ng-for instruction will be executed two times.

Example in this plunker: http://plnkr.co/edit/tFGJVjO3z78GEXCTKFh4?p=preview

I think the framework need report an error with this info or render only one time the ng-for...

Thanks and sorry my bad english 😄

@pkozlowski-opensource
Copy link
Member

Right, we are aware of this, see #2568.

@tbosch would you have any pointers as where would be the best place of fixing this one. I had a quick look at the code and the fact that directives can be both a type and a binding makes things slightly more complex - that it - we need to wait with duplicate removal till bindings are resolved and I'm not sure where to stick this logic...

@l-Leniac-l
Copy link
Author

Ok Thanks!

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants