886606 - [email] Implement representation checking in FolderStorage for header/body additions/modification

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[Andrew Sutherland [:asuth] (he/him)]

Per discussion at last week's in-person pow-wow, we want to validate data that we are persisting to disk or other long-term storage.  This will be useful for unit tests and ideally to avoid problems in the field where bad data gets into the system and breaks it forever.

In practice, bad data like that can be troublesome if we lack the ability to put a special marker that tells synchronization logic to avoid synchronizing whatever it is again in the future.  Otherwise we can get into a bad sync loop or an inefficient state where sync completes but every time we go to sync we try and re-sync the thing in question.  So when we fix this, it might be nice to implement this so that we just silently drop bad data in a way that avoids re-synchronizing the message in the future.  Like drop bad body parts and/or put a flag on the message indicating it's corrupt for some reason.

Comment 1

[Andrew Sutherland [:asuth] (he/him)]

Paragraph 1 was what this bug was about, and this was just now sufficiently fixed as part of bug 871897, see mail_rep.js.  I have spun off paragraph 2 in a slightly more general fashion on bug 943802.