qubit-redact-derive

Qubit Redact Derive provides procedural macros for the qubit-redact runtime crate. Use them to define a deliberate redaction boundary for Rust domain objects: create safe borrowed diagnostic views with Redact, or explicitly replace logical values with RedactMut.

Why qubit-redact-derive

• Field annotations make masking, omission, nested redaction, and map redaction reviewable at the domain-model boundary.
• The macros support named, tuple, and unit structs, plus enums with all three variant shapes.
• Optional Serde support serializes a redacted view without granting it deserialization or exposing an original-value escape hatch.
• The generated code resolves a direct qubit-redact dependency, including a Cargo-renamed dependency, instead of relying on a fixed import spelling.

Quick Start

Add the runtime and derive crates together:

[dependencies]
qubit-redact = "0.4"
qubit-redact-derive = "0.4"

use qubit_redact::Redact as _;
use qubit_redact_derive::Redact;

#[derive(Redact)]
struct Credentials {
    user: String,
    #[redact(level = "secret")]
    password: String,
}

fn main() {
    let credentials = Credentials {
        user: "ada".to_owned(),
        password: "raw-password".to_owned(),
    };

    let output = format!("{:?}", credentials.redacted());
    assert!(output.contains("ada"));
    assert!(!output.contains("raw-password"));
}

Redact creates a borrowed view. The original Credentials value remains available to application logic.

For types whose fields must all be reviewed explicitly, add #[redact(require_explicit)]. Mark intentionally visible fields with #[redact(plain)]; the default behavior remains unchanged for existing types.

Choose a Derive

Use Redact for diagnostics whenever possible. Choose RedactMut only when the next boundary requires a logically replaced value.

Attribute Overview

Field attributes select exactly one handling mode:

Container attributes are opt-in controls:

Unmarked fields use their ordinary Debug representation by default. They are neither masked nor recursively traversed. require_explicit changes only the derive invocation where it is written.

Field sensitivity classification belongs to the downstream application and its domain-model owners. This derive cannot determine whether a field is sensitive in a particular product, so it intentionally does not require every field to carry an attribute. Applications should mark the fields that cross their redaction boundary and choose plain only when ordinary visibility is an intentional, reviewed decision. require_explicit is available for models whose review policy requires every field to make that choice.

When #[redact(serde)] is enabled, deserialization-only Serde controls such as default, alias, skip_deserializing, and deny_unknown_fields are accepted and ignored by the generated serialization. Structural or serialization-side controls that could bypass redaction remain rejected. Serialization adapters (with and serialize_with) are accepted only on plain or skip fields. A plain adapter intentionally receives the original field value; redaction modes that inspect raw state reject adapters so they cannot bypass the generated redaction.

Dependencies and Features

The generated code requires qubit-redact to be a direct dependency. The derive crate discovers Cargo renames, so this also works:

[dependencies]
redaction = { package = "qubit-redact", version = "0.4" }
qubit-redact-derive = "0.4"

To use #[redact(serde)], enable the runtime crate's serde feature and declare serde directly:

[dependencies]
qubit-redact = { version = "0.4", features = ["serde"] }
qubit-redact-derive = "0.4"
serde = { version = "1", features = ["derive"] }
serde_json = "1"

#[redact(json)] requires the runtime crate's json feature. It formats a redacted JSON view, rewrites the string as compact redacted JSON for RedactMut, and serializes as a JSON string when combined with #[redact(serde)].

The derive package's test-json feature is only for its own test suite; it does not enable runtime features for downstream crates.

Safety Boundaries

• The macros protect only the redacted view, generated formatting, or explicit in-place operation that you use. They cannot protect unrelated log calls or serialization paths.
• An unmarked field uses its own Debug output. Mark every field whose representation can disclose sensitive data, or opt into #[redact(require_explicit)] and use #[redact(plain)] for intentional pass-through fields.
• skip omits a value from the redacted representation; it does not erase the original value.
• RedactMut performs logical replacement only. It does not erase released allocations, aliases, copies, or borrowed backing storage.
• debug and display use the process-wide default policy. Use an explicit redacted_with boundary when a call site needs policy isolation. Redacted Debug output uses the policy diagnostic output budget by default. Nested, map, and JSON fields share the same diagnostic session for one redacted view, so they cannot independently reset that budget.
• Do not use skip_serializing_if with level, nested, map, or json; its predicate receives the raw field and could reveal sensitive state through field presence. It is supported only with plain and skip fields.

Learn More

• English User Guide and 中文用户手册
• Runtime README and runtime user guide
• Runtime API documentation
• Derive API documentation

Testing

# Run tests with the default feature set
cargo test

# Run tests with all declared features
cargo test --all-features

# Project CI checks
./ci-check.sh

# Check code coverage
./coverage.sh

License

Copyright (c) 2025 - 2026. Haixing Hu. All rights reserved.

Licensed under the Apache License, Version 2.0. See LICENSE for the full license text.

Contributing

Contributions are welcome. Please follow the Rust API guidelines, keep public API documentation and tests current, and run ./align-ci.sh to format code and ./ci-check.sh to satisfy CI requirements before submitting a pull request.

Author

Haixing Hu - Qubit Co. Ltd.

Repository: https://github.com/qubit-ltd/rs-redact-derive