ngRepeat: property names starting with "$" will not be rendered

[mgmeyers]

When using ngRepeat to iterate over an object, it will not output any key-value pair where the key starts with a dollar sign ($).

Here is a demo:
http://jsfiddle.net/takvg/4/

And, the actual code in question can be found here: https://github.com/angular/angular.js/blob/master/src/ng/directive/ngRepeat.js#L284

if (isArrayLike(collection)) {
  collectionKeys = collection;
  trackByIdFn = trackByIdExpFn || trackByIdArrayFn;
} else {
  trackByIdFn = trackByIdExpFn || trackByIdObjFn;
  // if object, extract keys, sort them and use to determine order of iteration over obj props
  collectionKeys = [];
  for (key in collection) {
    if (collection.hasOwnProperty(key) && key.charAt(0) != '$') {
      collectionKeys.push(key);
    }
  }
  collectionKeys.sort();
}

Specifically:

key.charAt(0) != '$'

I'm assuming this is to prevent angular's internal properties from being iterated over by ngRepeat. I would suggest removing this limitation, but I don't know enough about the internals or the reasoning behind this to know what effect that might have.

[ashleygwilliams]

hey @mgmeyers! thanks for submitting this issue!

however, i think the cost of implementing this would out-weigh the benefits. is there a specific scenario where you are being forced to use a hash with a key that begins with a '$'? if so, please reply back and we can reopen and discuss.

[DexterMorg4n]

Yes, there are many. $ is a common prefix for other frameworks that work with front end frameworks like Angular. That makes angular useless in creating dashboard config panels, route configuration for other software, JSON editors used for many many developments

[rodyhaddad]

I believe this should be fixed, or at least discussed more

[IgorMinar]

fiddle updated to 1.3.0: http://jsfiddle.net/takvg/4/

[IgorMinar]

maybe we could make stuff we want to hide non-enumerable properties and have ng-repeat ignore those.

that would be a small code change, but the side-effects are hard to estimate, so let's not do this in 1.3.0.