A word to explain the prototype inheritance problem of ANGULARJS scope

When a stereotype inherits, the assignment to a variable does not modify the value in the stereotype, but instead creates a property with the same name directly in the current scope, but if the variable is an object, it is not created.

In a word, the base type will re-create the variable, and the reference will not. This explains that "the angularjs often occurs in a two-way binding (when a child scope, such as a ng-repeat) occurs, the direct binding string variable is unsuccessful, but it is bound to be successful when the string is a property of an object."

See also for details: http://www.ngnice.com/posts/2c8208220edb94