I’m using the
Ember.computed.filter macro to filter a list of objects by a query field (called
filteredContacts: Ember.computed.filter "@this", (contact)-> ~contact.get('name').toUpperCase().indexOf @get("filterQuery").toUpperCase()
filterQuery changes, it won’t cause the computed array to recompute.
I noticed that custom defined arrayComputed and reduceComputed macros allow for multiple dependent keys, but most of the built-in macros just allow for one. Is there a reason for this? It feels dirty to define a mostly an identical custom filter macro just so I can have additional dependent keys.
I propose to modify the built-in macros to handle multiple dependent keys.