You found a bug! We've classified it as
TOUCH-3727
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
-
Sencha User
We hit upon the same problem. Should be fixed in an upcoming version of Sencha Touch
-
16 Apr 2013, 11:15 PM
#12
Sencha User
I haven't updated my app yet, but looking at the source code it looks like this issue hasn't been fixed in 2.2.0.
It's closed, so unless somebody reopens it again it will never get fixed.
-
Sencha User
This bug also affects stores using memory proxies. Then you can just do:
and immediately see it ignored, and the previous value retained. I'm still seeing this in sencha 2.2.1. I fixed it with an override of Ext.data.reader.Reader, but that's a pain to maintain.
It's obvious that no data is a valid, non-error condition, and shouldn't be treated as an error.
-
Sencha User
I'd like to second this bug. It's not just with Ajax proxies; it affects all proxies. Here's an example:
Code:
Ext.define('User', {
extend: 'Ext.data.Model',
config: {
fields: [
{name: 'id', type: 'int'},
{name: 'name', type: 'string'},
{name: 'phone', type: 'string', mapping: 'phoneNumber'}
]
}
});
var store = Ext.create('Ext.data.Store', {
model: 'User',
data : [],
proxy: {
type: 'memory',
reader: {
type: 'json'
}
}
});
store.load({
callback: function(records, operation, success) {
console.log(success); // logs "false"
}
});