Filters are broken in Sencha Touch 2?

Hello,

I have a page where filters are set, then I have a store which is loaded with a new data from the server. Here's how I do it:
1) On the filters page I have controls for setting values. Controller listens tothose events and creates the custom this.filter object. Basically that is a list of filters:

It actually clears all filters and add only those I need.
4) This results in a correct XHR request:
GET /deal
_dc:1324713983633
page:1
start:0
limit:25
filter:[{"property":"isOffer","value":false}]
5) I get the data back and in the loadRecords method (Sencha internals) everything is fine - 25 records are loaded, but then since filterOnLoad is true by default it tries to filter the data and here's where we get problems.
The filter I have is {"property":"isOffer","value":false}. I have a lot of models that come from server that have isOffer=false.
By the way, here's is the model definition:

6) After filtering I see no records in the store (yeah, they are in the snapshot, but that's not what I'm talking about).
7) Problem occurs because Sencha creates the filterFn and value matcher that are used in filterBy function. This is correct, but instead of checking model.data properties, they are checking just model properties:

Yes, this is my problem, but given that filters are most commonly used in the stores and stores may only contain models, isn't it a good idea to set this option to 'data' by default to make the framework behave more predictable?

I cannot thing of a usecase when someone filters anything except models, do you? If not, I'd like this to be recorded as a feature request

Yes, this is my problem, but given that filters are most commonly used in the stores and stores may only contain models, isn't it a good idea to set this option to 'data' by default to make the framework behave more predictable?

I cannot thing of a usecase when someone filters anything except models, do you? If not, I'd like this to be recorded as a feature request

You can filter a custom Ext.util.MixedCollection but 99.9% of the cases out there will be filtering on a Store. Therefor I tend to agree with this so I am opening a ticket and letting the core devs ultimately decide on this change.

I use MixedCollections in my code more often than not... they are actually quite useful. Like the items property on a component, it's a MixedCollection and I have use-cases that I've filtered and sorted them based on app logic and that made it quite easy.