Check TOON row counts and inspect the decoded JSON
Admin ·
Check a TOON document before using it as data. Strict validation compares array declarations with the supplied rows. The decoded JSON lets you check whether valid syntax produces the values and types you intended.
Validate the two-row table
Paste the example into TOON input and select Validate TOON. The header declares two records with id and active fields. In Decoded JSON, the second object's id is 10 and its active value is the boolean false.
items[2]{id,active}:
7,true
10,falseSeparate a row-count error from a wrong value type
Change [2] to [3] and validate again. The tool flags line 3 and asks you to check the declared counts and row widths. The header expects three tabular rows but the document contains two. Restore [2] if the table is complete. If it lost a record in transit, restore the row from the source data first.
With [2] restored, change the last false to "false" and validate. The table passes the syntax check. The decoded JSON now shows "active": "false" for the second record. Remove the quotes if active is supposed to be a boolean.
Official TOON format specificationRFC 8259, the JSON data interchange format
Download JSON once the values match your expectations
After you restore the intended boolean, validate and download decoded.json. The items array should contain exactly two objects, with numeric ids and two boolean active values.
For a saved table that still fails validation, compare the number of cells in each row with the field list. Check the delimiter declared between the brackets and keep each row at the same indentation beneath its header.
Common questions
What does a successful TOON check establish?
The supplied document decoded under strict format rules. Compare its values with your schema or intended data before importing it.
Should I remove quotes around id values to fix a count error?
Keep the intended types. Repair the count or restore missing rows, then compare the decoded identifiers with the original data.