[4.1.0] 'id' field leak

[mankz]

Ext.define('foo', {
   extend : 'Ext.data.Model',
   fields : ['bar']
});

foo.prototype.fields.length; ==> 2

Seems the 'id' field leaks into all subclassed models (breaks deserialization in ASP.NET for example).

[scottmartin]

Thank you for the report.

Regards,
Scott.

[Misiu]

Any updates on this one? I and probably most of developers would like this fixed.
id field should be default, but using some property we should be allow to overwrite this.

Something like:

Ext.define('foo', {
   extend : 'Ext.data.Model',    
   idProperty : 'Id',//this is what we need!
   fields : [{name : 'Id', type : 'string'},//here I would like to store user guid
             {name : 'Name', type : 'string'},
             {name : 'Department', type : 'string'}] 
  });

It isn't so hard to fix I guess

[keiths]

Any update on this? It is causing major problems for us.

[scottmartin]

This is currently slated for the 4.2 release.

Scott.

[keiths]

What is the estimated release date for 4.2?

[scottmartin]

In the near future

There is no public release date at this time.

Scott.

[Misiu]

I know that 4.2 beta was released just couple of hours ago, but is this tiny bug fixed in this release?

[mankz]

If you use 'idProperty', the bug is not reproducible.

[Animal]

It's not really a "leak"

It creates an id field for you based upon the default idProperty in Models which is "id"

A Model must have some identifier.

But if you really do not want that (eg an abstract base Model class), then you can

Ext.define('foo', {
   idProperty: null,  // No identifying field in this Model
   extend : 'Ext.data.Model',
   fields : ['bar']
});