Refactor scenario validation to support V2 schema and update related tests
- Updated `validate_scenario.py` to handle V2 scenario YAML files, introducing new required keys and validation logic. - Added support for legacy V1 scenarios with an option to allow migration. - Modified `run_content_checks.sh` to validate V2 scenarios and associated audio and printables manifests.
This commit is contained in:
+2
-2
@@ -7,12 +7,12 @@ Allowed scope:
|
||||
- `audio/generated/**` (derived outputs only after source changes)
|
||||
|
||||
Validate:
|
||||
- `python3 tools/audio/validate_manifest.py audio/manifests/zacus_v1_audio.yaml`
|
||||
- `python3 tools/audio/validate_manifest.py audio/manifests/zacus_v2_audio.yaml`
|
||||
- `rg -n "id:|file:" audio/manifests`
|
||||
|
||||
Common commands:
|
||||
- `rg --files audio`
|
||||
- `python3 tools/scenario/export_md.py game/scenarios/zacus_v1.yaml`
|
||||
- `python3 tools/scenario/export_md.py game/scenarios/zacus_v2.yaml`
|
||||
|
||||
Do not:
|
||||
- regenerate binary audio assets unless explicitly requested
|
||||
|
||||
Reference in New Issue
Block a user