-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Angular 1.2.0 stable is broken #1786
Comments
Ohhh shoot.. Derby made that decision in 0.5 as well, yeah we're using |
You know what - I was thinking, "well we can remove all our private fields from the app and come up with something cleaner" - and then remembered we have User._v. We're gonna have to wait this one out and follow that convo. |
Hopefully this pull request will be merged in 1.2.1 angular/angular.js#4859 |
Reverted in 1.2.1 👍 http://blog.angularjs.org/2013/11/angularjs-121-underscore-empathy.html |
Wooo! |
@lefnire just a reminder that angular 1.2.0 is broken.
They "decided" that all properties starting with a
_
are to be considered private so they can't be used inside the templates.It brokes a lot of thing and I don't feel we can change this easily.
The error is this http://docs.angularjs.org/error/$parse:isecprv?p0=_id and I really hope they'll revert the commit (angular/angular.js@3d6a89e) because it's completely preventig us to upgrade.
The text was updated successfully, but these errors were encountered: