How a null vs. undefined mismatch broke task editing in a Zod-validated app

A developer building FocusYar, a task management app, encountered a bug where editing a task without a priority field triggered an error reading 'There is nothing task.' The root cause was a mismatch between the value stored in the database — null — and the value the Zod validation schema was checking for — undefined. Because null, undefined, and empty string are treated differently in JavaScript, the preprocessing logic failed to convert the database value into an acceptable form before validation. The fix involved updating the Zod schema to check for null instead of undefined, allowing the empty priority field to pass through correctly. The experience highlighted the importance of tracing a value's actual state across every layer of an application — UI, database, schema, and server action — when debugging optional fields.