This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.5k
ng-model pointing to an expression containing square brackets fail if a middle value is undefined #8039
Milestone
Comments
rodyhaddad
added a commit
to rodyhaddad/angular.js
that referenced
this issue
Jul 8, 2014
… that use brackets notation Closes angular#8039
rodyhaddad
added a commit
to rodyhaddad/angular.js
that referenced
this issue
Jul 8, 2014
… that use brackets notation Closes angular#8039
rodyhaddad
added a commit
to rodyhaddad/angular.js
that referenced
this issue
Jul 9, 2014
… that use brackets notation Closes angular#8039
rodyhaddad
added a commit
to rodyhaddad/angular.js
that referenced
this issue
Jul 16, 2014
… that use brackets notation Closes angular#8039
Hi there, just wondering if this could be bumped up from "inconvenience" severity. It's a total blocker for me on json-schema-form/angular-schema-form#43 |
rodyhaddad
added
severity: broken expected use
and removed
severity: inconvenient
labels
Jul 27, 2014
rodyhaddad
added a commit
to rodyhaddad/angular.js
that referenced
this issue
Jul 27, 2014
… that use brackets notation Closes angular#8039
rodyhaddad
added a commit
that referenced
this issue
Jul 27, 2014
… that use brackets notation Closes #8039
@mike-marcacci We should have a new release next friday with the fix for this from #8113. You can use the latest snapshot to run your tests until the next release happens :-) |
You guys are awesome - definitely didn't expect a response until at least Monday. Cheers! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If I have a
ng-model
pointing to an expression which contains square brackets, and a middle value is undefined, an error like the following will be thrown:Example code:
I have tested this in v1.2.16 and then in v1.2.19. Both have the same problem.
Reproducible plunk: http://plnkr.co/edit/NKgyYDkqjOugjbNjWnmA?p=preview
The text was updated successfully, but these errors were encountered: