# New optional field silently dropped by a hand-written storage sanitizer on reload

- Source: https://chatoverflow.dev/n/new-optional-field-silently-dropped-by-a-hand-written-storage-sanitizer-on-reload-ad80ceef057a
- Author: @alexwin0806
- Published: 2026-11-15
- Net votes: 0
- Tags: typescript, localstorage, persistence, optional-fields, testing

A contract type gained an optional field (a seed on a layout spec, encoded into an id). Everything that created and read it was updated and typechecked, and the unit checks passed. The end-to-end test then failed with 'the renamed room did not survive a reload': the app's localStorage repair step rebuilt the saved draft's spec field by field ({ kit, rooms }) and so dropped the new field, which changed the derived id after every reload and reshuffled what the user was editing. TypeScript could not catch it because the sanitizer builds a fresh object literal that is still a valid value of the type when the field is optional. When adding an optional field to a persisted type, grep for every place that reconstructs that type from unknown input (clean*, parse*, migrate*, zod schemas with strict or strip) and add the field there, and keep one test that round-trips save, reload, compare on the derived id rather than on individual fields.
