Files
mizan/protocol/mizan-codegen/tests/rust_target.rs
Ryth Azhur 3aafec6dd4 A channel's message slots are named from the client, on every backend
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>
2026-07-27 14:03:19 -04:00

54 lines
1.8 KiB
Rust

//! Emits the Rust client crate, drops a consumer into its `tests/`, and runs
//! `cargo test` inside it. The consumer names every generated module path and
//! calls every generated function, so the emitted crate has to compile against
//! the real `mizan-rust` kernel before its serde round-trips are asserted.
mod harness;
use std::path::PathBuf;
use mizan_codegen::config::{Config, RustKernelSpec};
use mizan_codegen::emit::CodegenTarget;
use mizan_codegen::emit::rust::RustCrate;
fn crate_config() -> Config {
let kernel = harness::manifest_dir().join("../../frontends/mizan-rust");
assert!(
kernel.join("Cargo.toml").is_file(),
"the generated crate depends on the kernel at {}",
kernel.display(),
);
Config {
rust_kernel: Some(RustKernelSpec::Path { path: kernel.display().to_string() }),
rust_crate_name: "fixture_client".to_string(),
..harness::config_for("rust")
}
}
/// Build artifacts live outside the scratch root so a rerun reuses the
/// compiled kernel and its dependency tree instead of rebuilding them.
fn shared_target_dir() -> PathBuf {
harness::manifest_dir().join("target/toolchain-cargo")
}
#[test]
fn generated_crate_compiles_and_its_tests_pass() {
let root = harness::scratch_root("rust");
let ir = harness::load_ir("afi_ir.kdl");
harness::write_emitted(&root, &RustCrate.emit(&ir, &crate_config()));
harness::copy_fixture("rust_driver.rs", &root.join("tests/driver.rs"));
let cargo = harness::resolve_on_path("cargo");
let target_dir = shared_target_dir();
harness::run_tool(
&cargo,
&["test"],
&root,
&[("CARGO_TARGET_DIR", target_dir.as_path())],
"the emitted Rust client crate does not build or its consumer tests fail",
);
}