block

The block directive adds files and extension point contributions to the generated project. A manifest can contain any number of block directives. The label names the block in errors.

block "build_info" {
  description = "Build-time constants and their dependency."

  generates = {
    "src/build_info.rs" = "./codegen/build_info.rs.j2"
  }

  contributes = {
    "main::modules" = {
      kind     = "tokens"
      template = "./codegen/modules.rs.j2"
    }

    "cargo::dependencies" = {
      kind = "cargo_dependencies"
      crates = {
        const_format = {
          version  = "0.2"
          features = ["rust_1_64"]
        }
      }
    }
  }
}

Template paths resolve against the build context directory, like every other path in the manifest.

Contribution kinds

A contribution is an object whose kind field names its kind, alongside that kind's fields. Each extension point accepts one kind.

cargo_dependencies

crates maps a crate name to its dependency fields:

When several blocks declare the same crate, their fields are merged. A field set to different values fails the build.

Templates

Templates use Jinja2 syntax. The resolved manifest is available under ctx, for example {{ ctx.agent_name }} and {{ ctx.agent.version }}.

Interpolated strings in a generated file are escaped by its output path:

{{ value | safe }} writes a value as is in any file.

Composition

Manifest blocks are composed after the archetype, graph, and protocol blocks, in label order.

• Contributions to the same extension point are combined in that order, so a manifest block's contribution follows the built-in ones.
• A generates path that a built-in block also writes is written by the manifest block.

Errors