mirror of
https://github.com/Kelsidavis/WoWee.git
synced 2026-05-07 09:33:51 +00:00
b3e34e0edf
--info-jsondbc only verifies recordCount matches the actual records[] array length. This goes deeper, validating the full sidecar schema that --convert-json-dbc consumes: wowee_editor --validate-jsondbc db/Spell.json Checks: - top-level value is a JSON object - 'format' field exists, is a string, equals 'wowee-dbc-json-1.0' - 'source' field present (so re-import knows the DBC slot) - recordCount + fieldCount are non-negative integers - 'records' is an array; recordCount matches actual length - each record is an array exactly fieldCount cells wide - each cell is string|number|bool|null (no nested objects/arrays) Errors capped (3 per category) with '... and N more' tail so a 1000-row file with consistent breakage doesn't drown the report. Exit 1 on any error so CI can gate. Verified on a hand-rolled good JSON (passes clean) and a bad one with: wrong format tag, missing source, wrong-width row, and an object cell — all 4 issues reported with precise positions and exit 1. Format-validator lineup is now complete: Open binary: WOM / WOB / WOC / WHM / GLB Open text: JSON DBC Every shippable open format has a CLI validator that gates on schema/structure errors. |
||
|---|---|---|
| .. | ||
| asset_extract | ||
| auth_login_probe | ||
| auth_probe | ||
| blp_convert | ||
| dbc_to_csv | ||
| editor | ||
| asset_pipeline_gui.py | ||
| backup_assets.sh | ||
| diff_classic_turtle_opcodes.py | ||
| gen_opcode_registry.py | ||
| generate_ffx_sdk_vk_permutations.sh | ||
| m2_viewer.py | ||
| opcode_map_utils.py | ||
| validate_opcode_maps.py | ||