Struct cargo_culture_kit::HasContinuousIntegrationFile

pub struct HasContinuousIntegrationFile;

Rule that asserts a good Rust project: "Should have a file suggesting the use of a continuous integration system."

Justification

Continuous integration can reduce the odds of project functionality regression and several options are available to make this process accessible for Rust projects.

See also: https://github.com/japaric/trust

Trait Implementations

impl Default for HasContinuousIntegrationFile

fn default() -> HasContinuousIntegrationFile

Returns the "default value" for a type.

impl Debug for HasContinuousIntegrationFile

fn fmt(&self, f: &mut Formatter) -> Result

Formats the value using the given formatter.

impl Rule for HasContinuousIntegrationFile

fn description(&self) -> &'static str

The central tenet of this Rule. Serves as a unique identifier for Rule instances, as well as a human-readable summary of what this Rule means for a given project.

fn evaluate(&self, context: RuleContext) -> RuleOutcome

Does the Rust project found at cargo_manifest_path uphold this Rule, as summarized in the description?