octoturge
4cc40c913c
- print.schema.json, _ams.schema.json, _ams_unit.schema.json still pointed at the pre-rename filenames (ams.schema.json, ams_unit.schema.json, ams_tray.schema.json) after the underscore-prefix split - fixed all three, verified with a full jsonschema + referencing validation run against real captures (get_version, pushall, a full print/ams/xcam report with both empty and loaded trays) plus negative tests. - _upgrade_state.schema.json: fixed its $id (pointed at report/info/, file lives under report/print/) and its title (said "ModuleInfo", clearly copy-pasted from _module_info.schema.json). Wired it into print.schema.json as the print report's `upgrade_state` property - the file existed but nothing referenced it yet. - Deleted schemas/bambulab/v2/, which had been recreated as stale, broken copies of an older v1 (missing the envelope allOf, missing the underscore renames, $ids still pointing at v1/ paths) - the repo's own README documents v2 as intentionally removed until V2's wire format is known to differ from V1's. - Updated schemas/bambulab/README.md's layout tree and inheritance- example reference, both stale after the underscore rename. - Removed stray tsc -b build output (packages/ts-types/src/*.d.ts/js) that isn't meant to be committed (outDir is dist/, gitignored). Verified: cargo check clean (continuum-proxy, continuum-ai-worker, rust-types), tsc clean (continuum-backend, continuum-common ts-core), 10/10 JSON Schema validation cases passing.
38 lines
1.9 KiB
JSON
38 lines
1.9 KiB
JSON
{
|
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
"$id": "https://git.octoturge.com/Continuum/continuum-schemas/raw/branch/main/schemas/bambulab/v1/report/print/_ams_tray.schema.json",
|
|
"title": "AmsTray",
|
|
"description": "A tray slot is either empty (just `id`) or loaded (the full field set) - two genuinely different shapes for the same slot, not one shape with optional fields. oneOf says the instance must match EXACTLY one of these. Note LoadedTray requires every field it lists, not just `id` - with only `id` required, a bare {\"id\":\"0\"} would validate against BOTH branches at once (it trivially satisfies Loaded's single requirement too) and oneOf would fail, since oneOf demands exactly one match. Verified this the hard way - see git history. The Rust equivalent is an untagged enum with #[serde(deny_unknown_fields)] on the Empty variant, for the same reason in reverse: without it, a loaded tray's extra fields wouldn't be rejected by Empty, and untagged enums try variants in order - see bambu_commands/print.rs. `drying_time` and `drying_temp` fields are only available for AMS 2 and AMS HT - AMS 1 doesn't have the drying option.",
|
|
"oneOf": [
|
|
{
|
|
"title": "EmptyTray",
|
|
"type": "object",
|
|
"properties": {
|
|
"id": { "type": "string" }
|
|
},
|
|
"required": ["id"],
|
|
"additionalProperties": false
|
|
},
|
|
{
|
|
"allOf": [
|
|
{ "$ref": "./_vt_tray.schema.json" },
|
|
{
|
|
"title": "LoadedTray",
|
|
"type": "object",
|
|
"properties": {
|
|
"state": { "type": "integer" },
|
|
"total_len": { "type": "number" },
|
|
"ctype": { "type": "integer" },
|
|
"cols": { "type": "array", "items": { "type": "string" } },
|
|
"drying_time": { "type": "string" },
|
|
"drying_temp": { "type": "string" }
|
|
},
|
|
"required": [
|
|
"state", "total_len", "ctype", "cols"
|
|
]
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|