Hi to all.
In Ext 4.2.x I found a bug during the instantiation of a model that contains fields defined with the function "convert". Please refer to fiddle following:
http://ift.tt/1hb7H0X
The model "Model1" has two fields: "IDModel" and "Value", both of type "int". The "Value" field has the "convert" function, which in our example is limited to just return the value of the field.
Then we create a record from this model and if you go to check the values of its fields, the "IDModel" field has, correctly, the value of "null", while the "Value" field has, mistakenly, the value equal to a null string.
This is obviously a bug, since the correct value would have to be "null" and not a null string, which also violates the type of the field.
Bye.
Sergio.
In Ext 4.2.x I found a bug during the instantiation of a model that contains fields defined with the function "convert". Please refer to fiddle following:
http://ift.tt/1hb7H0X
The model "Model1" has two fields: "IDModel" and "Value", both of type "int". The "Value" field has the "convert" function, which in our example is limited to just return the value of the field.
Then we create a record from this model and if you go to check the values of its fields, the "IDModel" field has, correctly, the value of "null", while the "Value" field has, mistakenly, the value equal to a null string.
This is obviously a bug, since the correct value would have to be "null" and not a null string, which also violates the type of the field.
Bye.
Sergio.
Aucun commentaire:
Enregistrer un commentaire