Closed jrharshath closed 7 years ago
Yes, Harshath. That makes sense. However, I'm not yet sure in what direction should we move - to make this module closer to the Angular.js codebase or to make it a more independent third-party extension. We'll think about it, if we'll decide to make a 3.0 release.
Perhaps convert this into a PR for angularjs first, and then see how it turns out? :smile:
Angular already finds this feature wanting - check out this issue.
I've decided to stick to the current naming scheme for now. We should interfere with Angular namespace as little as possible.
This is only a suggestion. Since:
ng-model
's native behaviourngInputModified
instead of something that's not in angular's namespace (like bsInputModified)$pristine
is set to account formodified
(again affecting angular's standard behaviour)I propose we call our flag
$modified
. It would feel like a very fluid extension of angular's capabilities this way.Let me know what you think!