# Give omitted, null and blank different test cases

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Give omitted, null and blank different test cases

ID: MHC-D-RESEARCH-0982 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/give-omitted-null-and-blank-different-test-cases

An empty-looking cell can carry a very active instruction.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A mass update may clear existing values when the intended action was to leave them alone.

### Avoid when

- Do not standardize all missing representations into one value before checking their semantics. Different fields in the same interface can behave differently.

### Explanation

Write down how this exact interface represents no change, clear the value and set an empty string. Do not infer those meanings from appearance. JSON Merge Patch, for example, gives null a removal meaning; another interface may use an update flag or a different convention.

### Checklist

- Read the field-level update contract, including flags and defaults.
- Test omitted, null, empty-string and explicit-value inputs against an existing nonempty value.
- Inspect the stored result and any downstream message before approving a bulk run.

### Example

A file omits an email column in one test and includes it empty in another. Only the documented behavior determines whether either clears the address.

### Check

Each input state has an observed, documented target effect.

### Limits

- Do not standardize all missing representations into one value before checking their semantics. Different fields in the same interface can behave differently.

### Evidence and sources

- supports: JSON Merge Patch distinguishes an omitted member from a member set to null: null requests removal of that member. — RS-4FB38C20FE966683. This is one interface contract, not a universal interpretation of empty spreadsheet cells or null values. (Sections 1 and 2)
- RS-4FB38C20FE966683: RFC 7396: JSON Merge Patch — https://www.rfc-editor.org/rfc/rfc7396.html

### Vedokrok editorial review

Test what each empty-looking update will actually do

Omitting a field, removing it and storing an empty value are different instructions. Check the exact interface before a harmless-looking blank becomes a bulk change.

#### Keep the rule at the right level

For an object-member update in JSON Merge Patch, an omitted member is left alone, null removes the member, and an empty string sets an empty string. This is not a rule for every JSON value: a patch that is not an object replaces its target completely. A top-level null patch therefore replaces the document with null.

#### Inspect the stored result

In an isolated test record with a nonempty reference field, try omission, null, empty string and an explicit replacement separately. Record both the stored value and whether the field still exists. Test arrays separately if present; Merge Patch replaces them rather than editing selected elements. Check any downstream interpretation before applying the mapping to a real batch.

**Editorial takeaway:** Use the documented field and document rules, then verify the result. If the system needs a stored null to mean something distinct from removal, do not assume an object-member Merge Patch can express that change.

#### Editorial evidence

- supports: JSON Merge Patch distinguishes omitted object members, null-valued members and non-object patches. — RS-4FB38C20FE966683. The member-removal rule is scoped to object processing; the independent reference-field tests are an editorial application. (Section 2: MergePatch pseudocode and following paragraph; Appendix A)
- limits: Merge Patch does not support partial array edits and is not suitable for every JSON structure, particularly when explicit null object-member values matter. — RS-4FB38C20FE966683. Do not transfer these semantics to ordinary JSON storage, JSON Patch, spreadsheets or other import interfaces. Test the actual accepted media type and contract. (Section 1, final paragraph; Section 2; Appendix A, whole-target null example)
- RS-4FB38C20FE966683: RFC 7396: JSON Merge Patch — https://www.rfc-editor.org/rfc/rfc7396.html — Paul Hoffman, James M. Snell

Editorial version: 0.1.0 · evidence checked 2026-10-04 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/find-the-first-boundary-where-the-record-becomes-wrong
