Editor 1.6.4 with LOOSE type checking

Editor 1.6.4 with LOOSE type checking

geometrygeometry Posts: 22Questions: 6Answers: 0

I am running into this exact scenario with the original JSON data for the table containing numbers but the data retrieved from the editor being strings and hence being included in the "changed" data.

I see that 1.6.4 has introduced some loose checking by using the != comparison instead of !== but this only seems to work if the values are part of complex objects and not just simple values.

See the attached screenshot...

debug

This question has an accepted answers - jump to answer

Answers

  • allanallan Posts: 61,972Questions: 1Answers: 10,160 Site admin
    Answer ✓

    Hi,

    I've just added a reply in the other thread on this topic.

    Allan

  • geometrygeometry Posts: 22Questions: 6Answers: 0

    Thanks Allan. I made this one after I saw the other had been marked as "answered"

    Cheers again for being so quick with your support.

  • geometrygeometry Posts: 22Questions: 6Answers: 0
    edited August 2017

    Another case you may want to consider (for 1.6.5) is when the field is null/empty string?

    { description: null } for JSON data for the table from the server but
    { description: "" } from the editor is also included in "changed"

    This may be opening pandoras box with cases though.

This discussion has been closed.