is it possible to override default field converters?

[JakeLatham]

I'm wondering if I can override the default field conversion routines, rather than having to do it in each field.

For example, in our app, we have a lot of legacy code that returns "True" or "Yes" to what are boolean fields. rather than use ExtJS's built in parse for a 'bool' type field, I'd like to use my own convert function. However, rather than specify it every time:


...
{ name: 'copy', type: 'boolean', defaultValue: true, convert: BooleanUtilities.parse }, //some routine I wrote...
...


I'd like to be able to somehow override whatever does the type conversion for 'bool' type fields. Is this possible?

A similar case is where we have some legacy code that returns formatted integers for floats, such as "1,234" or "1,234.56". the standard int and float routines do not work for these, so I'd like to be able to do something like:



...
{ name: 'someValueField', type: 'float', defaultValue: true, convert: NumberUtilities.parse }, //can handle 1,234
...


Also, I noticed that when you specify a "convert", the field gets moved to the end of the field list, is there a way to prevent this?

-Jake

[vietits]

You can override Ext.data.Types (http://docs.sencha.com/ext-js/4-1/#!/api/Ext.data.Types) which is a singleton. However, I suggest you create new types instead of overriding the existing ones.

[JakeLatham]

Thank you - that did the trick most excellently.

Cheers!

-Jake