Ryth Azhur
3aafec6dd4
The IR called them react-message and django-message, so a FastAPI channel had to declare a DjangoMessage. They are client-message and server-message now, and the direction words hold wherever a channel is declared: Params / ClientMessage / ServerMessage, with mizan-core deriving <Pascal>Params and friends so no backend names a type itself. Django's ReactChannel and FastAPI's ReactChannel are both Channel. mizan-fastapi never registered a channels extension, so build_ir() emitted no channel at all and every payload type was invisible to codegen. It registers one now. RegistryExtension is an ABC requiring all(), which is what the IR reads — an extension that cannot enumerate its registrations no longer exists. The gate that should have caught the rename could not: tests/afi registered no channel because mizan-rust had no channel registry to register one in, so a five-package rename of the wire contract passed byte-parity without a channel byte crossing it. mizan-rust grows ChannelSlotKind, a CHANNELS slice, a #[mizan::channel] macro, and KDL emission whose wire_to_pascal matches Python's split; the AFI fixture now carries a channel with every slot and one with a single slot, so all three backends prove the contract byte for byte. MizanChannel held three Option<String> beside three has_*() predicates and unwrapped them with defaults; it holds an ordered slot vector, so an absent slot is absent rather than defaulted. The channels target emitted a React hooks file that a stage1-only consumer could not compile — react emits that now. The codegen's parity tests byte-compared emitted source against baselines without ever compiling it: they compile the generated crate and run its tests, import the generated Python package and call every method, and typecheck each TypeScript target against a consumer. Also fixed at source: app_visitor printed its import diagnostic to stdout, the stream export_mizan_ir writes KDL to, so a failed import silently corrupted the IR; the apps root was hardcoded to "apps"; _default_literal crashed build_ir on any non-JSON-serializable field default; Django and mizan-core derived Pascal names two different ways, disagreeing on every dotted channel name. ir.py builds a document and renders templates/ir/document.kdl.j2 rather than appending KDL strings with hand-tracked indentation, and named types resolve to a fixed point — a model reachable only through a union branch was referenced by a ref that no type block ever defined. The rest is the write-gate's own classifiers run over the standing tree: relative imports, silent swallows, Protocol contracts that should be ABCs, emitters hand-rendering target source, catch-all arms over closed enums, and comments narrating the project rather than the code. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
32 lines
1.1 KiB
Rust
32 lines
1.1 KiB
Rust
//! Emits the Python client as an importable package, drops a recording stand-in
|
|
//! for the PyO3 kernel beside it, and runs a consumer script under CPython. The
|
|
//! consumer imports the package, calls every generated method and reads the
|
|
//! Pydantic models back, so the emitted module has to import and execute.
|
|
|
|
mod harness;
|
|
|
|
use mizan_codegen::emit::CodegenTarget;
|
|
use mizan_codegen::emit::python::PythonClient;
|
|
|
|
|
|
#[test]
|
|
fn generated_package_imports_and_every_method_runs() {
|
|
let root = harness::scratch_root("python");
|
|
let ir = harness::load_ir("afi_ir.kdl");
|
|
harness::write_emitted(
|
|
&root.join("mizan_client"),
|
|
&PythonClient.emit(&ir, &harness::config_for("python")),
|
|
);
|
|
harness::copy_fixture("mizan_rust.py", &root.join("mizan_rust.py"));
|
|
harness::copy_fixture("python_driver.py", &root.join("driver.py"));
|
|
|
|
let uv = harness::resolve_on_path("uv");
|
|
harness::run_tool(
|
|
&uv,
|
|
&["run", "--no-project", "--with", "pydantic", "python", "driver.py"],
|
|
&root,
|
|
&[],
|
|
"the emitted Python client does not import or its consumer run fails",
|
|
);
|
|
}
|