You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wesley emit rust now emits basic Rust model declarations from Wesley L1 IR
through a structured Rust AST/printer projection. That proves the Rust-native
model path for consumer-shaped GraphQL contracts, but it is still a model
surface rather than a complete runtime binding.
The jedit hot-text fixture remains useful coverage because it pressures real
consumer shapes. It should not make Wesley own jedit product behavior.
Hill
Wesley can generate a Rust contract model layer that external consumers can
treat as shared artifact truth, without handwritten shadow models beside the
authored GraphQL schema.
Done looks like
generated Rust output is documented with examples
object, interface, input object, enum, union, scalar, list, nullability, and
reserved-word behavior are covered by golden tests
generated models can be consumed by an external Rust crate without local
structural rewrites
serde behavior, crate imports, and custom scalar hooks are configurable enough
for real consumers
operation/protocol generation has an explicit owner and does not get smuggled
into the basic model emitter
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Migrated from a local Wesley Method backlog card after adopting METHOD v2.1.0 tracker doctrine.
docs/method/backlog/bad-code/SOURCE_rust-emitter-consumer-model-parity.mdbad-codelane:bad-codeSOURCEOriginal Local Backlog Card
Rust emitter consumer model parity
bad-codeSOURCEWhy now
wesley emit rustnow emits basic Rust model declarations from Wesley L1 IRthrough a structured Rust AST/printer projection. That proves the Rust-native
model path for consumer-shaped GraphQL contracts, but it is still a model
surface rather than a complete runtime binding.
The jedit hot-text fixture remains useful coverage because it pressures real
consumer shapes. It should not make Wesley own jedit product behavior.
Hill
Wesley can generate a Rust contract model layer that external consumers can
treat as shared artifact truth, without handwritten shadow models beside the
authored GraphQL schema.
Done looks like
reserved-word behavior are covered by golden tests
structural rewrites
for real consumers
into the basic model emitter
Repo Evidence
crates/wesley-emit-rust/src/lib.rscrates/wesley-cli/src/main.rstest/fixtures/consumer-models/jedit-hot-text-core.graphqlcrates/wesley-emit-typescript/src/lib.rs