Yesterday I spent some time understanding why a user was complaining that its client reported that the record was modified when switching to the tree view although he didn’t change anything.
The reason is that there is an additional key in the dictionary sent to client which of course results in the fact that
old_value ≠ current_value as the current value is computed from the displayed data.
I understand that but I don’t remember if we discussed the idea of validating only the keys that are defined by the
DictSchema . It could be a good idea, because that way if people for some reason add a key to the dict (for the use in an external service) we wouldn’t meddle with ‘their’ data … it’s a bit like we don’t care about additional columns.
What do you think about this?