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

"TypeError: Cannot read property 'name' of null" after updating to v0.2.11 #1332

Closed
sorenhoyer opened this issue Sep 3, 2014 · 4 comments · Fixed by #1361
Closed

"TypeError: Cannot read property 'name' of null" after updating to v0.2.11 #1332

sorenhoyer opened this issue Sep 3, 2014 · 4 comments · Fixed by #1361
Labels
Milestone

Comments

@sorenhoyer
Copy link

dsfd

        <ul id="adminmenu" >
            <li ng-repeat="item in settings.menu.items" ui-sref-active="has-current">
                <a class="first-item" ui-sref="{{item.uiSref}}">{{item.name}}</a>
                <ul class="submenu">
                    <li ui-sref-active-eq="current" ng-repeat="subitem in item.items">
                        <a ui-sref="{{subitem.uiSref}}">{{subitem.name}}</a>
                    </li>
                </ul>
            </li>
        </ul>

The error is occuring on line 248 if you have an angular binding as the ui-sref:

a class="first-item" ui-sref="{{item.uiSref}}">{{item.name}}

It worked perfectly fine in previous versions and I think it's kind of important being able to dynamically set the sref - at least I know I absolutely require it for the CMS I'm building.

Any clever advice on this? :-)

Thanks

@sorenhoyer
Copy link
Author

I was able to find a fix here on git:

#1314

More precisely this did the trick: kz26@11a423d

Thanks to kz26

@christopherthielen christopherthielen added this to the 0.2.12 milestone Sep 4, 2014
@christopherthielen
Copy link
Contributor

thanks @sorenhoyer @kz26

@christopherthielen
Copy link
Contributor

@gise88 thanks, this looks like a legit bug. Can you open a separate issue please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants