This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
ngModelController is semi-useless with scope:truthy #6199
Description
Activity
Well, it seems like you've answered your own question here :p You really need to wrap primitives which is to be shared between scopes in objects.
I've suggested using ES6 proxy objects to get around this in the future (for transcluded scopes), but for child scopes I'm not totally sure what can be done about this. Maybe there is some pattern that could make all of this transparent, I'm not sure.
In the mean time though, I don't think this is really actionable. I'm not sure if I want to close this, but I'll see what other people think.
- added this to the milestone
on Feb 10, 2014
Since using
scope:truthyon a directive creates a new scope, theng-modelattribute no longer refers to the model the user intended, but instead is now one level deeper. This creates an unexpected behavior when someone is, say, using$scope.valinstead of$scope.obj.val.I don't know of any elegant way to work around this problem other than to not leverage ngModelController (which seems like poor design). Is there perhaps any way to ensure the ngModel is evaluated on the outer scope (such as by changing directive priorities) but can be accessed/modified by directives with a deeper scope?
This issue is in response to angular-ui/ui-select#18 (pinging @tkrotoff)