Struct BoundaryViolation 

pub struct BoundaryViolation {
    pub from_path: PathBuf,
    pub to_path: PathBuf,
    pub from_zone: String,
    pub to_zone: String,
    pub import_specifier: String,
    pub line: u32,
    pub col: u32,
    pub via_path: Option<PathBuf>,
}

An import that crosses an architecture boundary rule.

Fields

from_path: PathBuf

The file making the disallowed import.

to_path: PathBuf

The file being imported that violates the boundary. When the import goes through a re-export chain, this is the origin module that declares the imported symbol, not the barrel.

from_zone: String

The zone the importing file belongs to.

to_zone: String

The zone the imported file belongs to.

import_specifier: String

The raw import specifier from the source file.

line: u32

1-based line number of the import statement in the source file.

col: u32

0-based byte column offset of the import statement.

via_path: Option<PathBuf>

The barrel file that the source file imports directly, when the violation comes from a re-export chain. Absent for a direct import.

Trait Implementations

impl Clone for BoundaryViolation

fn clone(&self) -> BoundaryViolation

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for BoundaryViolation

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for BoundaryViolation

fn deserialize<__D>( __deserializer: __D, ) -> Result<BoundaryViolation, <__D as Deserializer<'de>>::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl JsonSchema for BoundaryViolation

fn schema_name() -> Cow<'static, str>

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn inline_schema() -> bool

Whether JSON Schemas generated for this type should be included directly in parent schemas, rather than being re-used where possible using the $ref keyword.

impl Serialize for BoundaryViolation

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.