Fix a Zero-Value Bug With a Small Test

A runnable JavaScript example: preserve a valid zero, inspect a proposed fix, and test the missing-value cases.

Reviewed: 2026-10-14
Read time: About 3 min

Audience and review notes

For: Developers practising a small, reviewable AI-assisted code change.

Check facts against original sources and remove sensitive information. Review AI output before relying on it.

On this page

The Task

A fictional delivery form allows a customer to enter zero reminder days. The application silently changes zero to seven. Fix that behavior without changing how an omitted value works.

This is an editorial worked exercise, not a comparison of assistant quality. The JavaScript test below was run locally for this example. The prompt is a reusable request; the proposed response is illustrative, not a captured vendor run.

Input: The Bug And Its Contract

The original expression is value || 7. JavaScript treats zero as falsy, so the fallback replaces a valid value.

For this exercise, the caller supplies a non-negative integer, null, or undefined. Preserve integers including zero; use seven only for missing values. Parsing form strings and rejecting other input belong to the caller and are outside this patch.

Give The Assistant A Bounded Request

Fix reminderDays(value), currently implemented as return value || 7.
Input contract: non-negative integer, null, or undefined.
Preserve 0 and positive integers. Default null and undefined to 7.
Return one minimal change, explain the behavior, and provide tests.
Do not add a dependency or change input parsing. List assumptions.

Inspect A Proposed Change

A tempting suggestion is value === 0 ? 0 : value || 7. It handles the reported zero, but leaves the original broad fallback in place. A more direct expression of this contract is value ?? 7: default only null and undefined.

Neither expression validates arbitrary form input. For example, the new one preserves an empty string. If your real application expects an empty string to mean missing, update the contract and tests before applying this patch.

Run The Reproduction And Regression Tests

Run the following as a Node.js .mjs file using the built-in assertion module. It first demonstrates the old behavior, then checks the intended replacement.

import assert from "node:assert/strict";

const original = (value) => value || 7;
const reminderDays = (value) => value ?? 7;

assert.equal(original(0), 7); // Reproduces the bug.
for (const [input, expected] of [
  [0, 0], [1, 1], [14, 14], [null, 7], [undefined, 7]
]) {
  assert.equal(reminderDays(input), expected);
}
console.log("PASS: zero is preserved; missing values default to seven.");

Expected output: PASS: zero is preserved; missing values default to seven. In the sample run, all five replacement cases passed. That result covers this function’s stated contract, not an entire application or its security.

Before Merging In A Real Project

Find the caller and confirm whether it sends numbers or strings.
Check that the project’s runtime supports the syntax.
Run the surrounding form and notification tests, including a manual zero input.
Inspect the final diff for unrelated changes and keep private data out of prompts.

The deliverable is a one-line behavior change plus focused tests. Record the actual results in your change description, including anything you did not test.

Continue

Use the code review checklist for a larger change, or compare Coding Tools. Save candidates in your shortlist to revisit their announcement checks on the homepage.