Render unknown stock separately from zero
Buyers mistake missing quantities for zero because the grid coerces null. Preserve the API distinction.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Rendering · Data contracts
Estimated field mix
- Frontend80%
- API design20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional supplier Reedworks uses a browser inventory table. Quantities are planning records, not live warehouse instructions.
Setup prerequisites
- Create synthetic SKUs with revisions and nullable quantities.
- Implement a local paginated adapter with conditional updates.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Null displays Unknown
- Zero displays 0
- Unknown values sort last
Implementation constraints
- Do not mutate stored quantities.
Verification to include
- Render null beside zero
- Reject nonnumeric values without showing NaN
Deliverables
- Quantity renderer and cases
Rollout and recovery
Revert the renderer without migration.
Value of the work
For the engineer: Practice grid interaction and concurrent edit recovery.
For the team: Inspect how changes protect operator intent during partial failures.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.