Function generate_code 

pub fn generate_code(
    metadata: &CodeGenMetadata,
    config: &CodeGenConfig,
) -> Result<()>

Generate all code described by config from metadata.

Writes the following outputs, depending on which CodeGenOutput fields are Some:

Field	Contents
output.common	Axum request extractors (extractors/<service>/) and their mod.rs
output.models	labels.rs (with generate_resource_enum), pyo3_impls.rs (with output.python) and the mod.rs mounting the models, in the models_subdir
output.server	Handler trait + Axum route wiring per service
output.client	HTTP (and/or ConnectRPC) client structs and request builders per service, plus the aggregate client
output.python	PyO3 binding wrappers (and the Python package files)
output.node	NAPI binding wrappers
output.node_ts	TypeScript client (client.ts, models/index.ts)
output.wasm	#[wasm_bindgen] bindings (mod.rs) and client.d.ts

Required fields

• output.server needs output.common (the extractors).
• bindings must be Some when any of output.python, output.node, or output.node_ts is Some; otherwise returns Error::MissingBindingsConfig.
• models_path_template and models_path_crate_template must be valid Rust path templates (containing {service}); invalid templates return Error::InvalidModelsPathTemplate.

Optional fields

Setting generate_resource_enum to false skips labels.rs generation. Setting bindings to None skips all language-binding output.

Call CodeGenConfig::validate before this function to surface config errors at construction time rather than mid-generation.

Errors

Returns:

• Error::InvalidModelsPathTemplate if models_path_template or models_path_crate_template is not a valid Rust path template.
• Error::InvalidConfigPath if context_type_path or result_type_path is not a valid Rust path.
• Error::MissingBindingsConfig if any of the python, node, or node_ts outputs is requested without a bindings config.
• Error::Build if a REST client or Python option lacks an option it needs.
• Error::MissingAnnotation or Error::Build surfaced while analyzing the metadata (e.g. a required google.api annotation is missing, or a service cannot be planned).
• Error::InvalidRustPath if a proto message or field maps to an invalid Rust path, and Error::InvalidErrorTypePath if the configured error_type_path is not a valid Rust path.
• Error::GeneratedParse if an internal generator produces tokens that do not parse as a Rust file.
• Error::Io if creating the models directory or writing any generated file fails.