9

Can anyone explain to me the purpose of arrangedContent.

The docs explains that it can be overriden in subclasses:

The array that the proxy pretends to be. In the default ArrayProxy implementation, this and content are the same. Subclasses of ArrayProxy can override this property to provide things like sorting and filtering.

What I am confused is its relationship with content. I can see in the source that it has a computed property on the content:

arrangedContent: Ember.computed('content', function(){
  return this.get('content');
}

I think I am in right in saying that you should never bind to the content but instead bind to the arrayProxy itself.

I am assuming that the same holds for arrangedContent?

Do I just use the arrangedContent to filter the array as I need it and bind to the arrayProxy itself or am I missing something?

dagda1
  • 26,856
  • 59
  • 237
  • 450

1 Answers1

11

You're totally correct: you should always target the proxy itself when binding to values or triggering methods like addObject. Having an arrangedContent allows Ember to manipulate properties of the collection like its sort order or selected item without changing these on the underlying array.

Since a single array of objects can be the underlying data for many parts of an application, you wouldn't necessarily want to change the array itself.

Jame's Croft has a great guide talking about Proxies: http://matchingnotes.com/ember-array-proxy

Rajat
  • 32,970
  • 17
  • 67
  • 87
Trek Glowacki
  • 3,621
  • 1
  • 17
  • 16
  • If I have a computed property only on content, as above, the arrangedContent computed property is only triggered when the array is initialised. I thought it might be triggered when it was bound to a handlebars template. Is there something else I should be doing? – dagda1 Oct 22 '12 at 12:26
  • 1
    Plus a million if I could, for the linked guide. A *very* well written tutorial on ArrayProxy that was the answer I did not know I was looking for. – chris Dec 08 '14 at 15:47