Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
Define the contract for each field rather than treating these cases as identical. Validate required data and tolerate harmless additions when the contract allows it.
A missing key can mean a default applies, while an explicit null can represent an intentional absence. Unknown fields may be safe to ignore, but unknown enum values need a deliberate fallback or error. Avoid defaults that turn invalid money or identifiers into apparently valid data. Test realistic schema variations and make decoding failures diagnosable.