-
Notifications
You must be signed in to change notification settings - Fork 3k
ui-view in ng-repeat issue after migrating to 0.2.8 #794
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
Comments
I'm not sure using a ui-view within an ng-repeat is a very good idea though... because then the child state would have to explicitly populate each ui-view based on its name, but if its dynamic that may be difficult. |
true, the plunker example is not showing a real world example. in my case inside the repeat there's ng-if directive that expects stateParam with the id of an item that was clicked. |
While I think there is probably a better way to architect something like this, I guess it is still a valid bug. Unfortunately it just won't be top priority at the moment. Will you be able to think of a different way to achieve the same results in the meantime? |
Oh is this a regression? If so, hopefully it will just become fixed once #774 is fixed. |
Closing to keep convo focused on #774. |
replace the text to
<ui-view></ui-view>
will get the js infinite evaluation.this will get your browser stuck in loop so watch out.
this issue might be related to #774
http://plnkr.co/edit/ZyjOx6oStZxrpFtfgrxr?p=preview
The text was updated successfully, but these errors were encountered: