阅读中文版

These inputs demonstrate reproducible behaviour; they are not customer incidents or evidence of real usage.

Reproducible input

{"status":"pending","status":"paid"}

Steps

  1. Load the sample and press Format. Both status fields remain in the formatted output.
  2. Read the duplicate-key warning at /status. Use Locate to select the conflicting key.
  3. Check the producing service and the intended status with the data owner before removing either value.

Expected result

The tool warns about a duplicate key and preserves pending and paid. Sending this input to YAML conversion is blocked rather than silently choosing one.

Limits and manual checks

This tool detects a conflict; it cannot decide which status is correct. JSON member names should be unique, but parser behavior differs. Never repair business meaning by guessing.

Technical reference

Return to the task and choose the next check