Struct MD077ListContinuationIndent 

pub struct MD077ListContinuationIndent { /* private fields */ }

Rule MD077: List continuation content indentation

In both tight continuation (no blank line) and loose continuation (after a blank line), content must not be over-indented beyond the item’s content column. Additionally, in loose continuation content must not be under-indented below the content column (W+N rule), or it falls out of the list; tight under-indent is valid CommonMark lazy continuation and is left alone. Content indented to the content column + 4 or more is an indented code block, not continuation, and is not flagged.

Under the MkDocs flavor, a minimum of 4 spaces is enforced for ordered list items to satisfy Python-Markdown.

With style = "aligned", tight under-indented continuation is additionally flagged and aligned to the content column (mdformat parity).

Implementations

impl MD077ListContinuationIndent

pub fn new(style: ContinuationStyle) -> Self

Construct the rule with an explicit continuation style. Default (ContinuationStyle::Any) preserves the historical behavior.

pub fn from_config_struct(config: MD077Config) -> Self

Trait Implementations

impl Clone for MD077ListContinuationIndent

fn clone(&self) -> MD077ListContinuationIndent

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Default for MD077ListContinuationIndent

fn default() -> MD077ListContinuationIndent

Returns the “default value” for a type.

impl Rule for MD077ListContinuationIndent

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

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

fn check(&self, ctx: &LintContext<'_>) -> LintResult

fn fix(&self, ctx: &LintContext<'_>) -> Result<String, LintError>

fn category(&self) -> RuleCategory

Get the category of this rule for selective processing

fn should_skip(&self, ctx: &LintContext<'_>) -> bool

Check if this rule should quickly skip processing based on content

fn as_any(&self) -> &dyn Any

fn default_config_section(&self) -> Option<(String, Value)>

Returns the rule name and default config table if the rule has config. If a rule implements this, it MUST be defined on the impl Rule for ... block, not just the inherent impl.

fn from_config(config: &Config) -> Box<dyn Rule>

where Self: Sized,

Factory: create a rule from config (if present), or use defaults.

fn config_aliases(&self) -> Option<HashMap<String, String>>

Returns config key aliases for this rule This allows rules to accept alternative config key names for backwards compatibility

fn polymorphic_config_keys(&self) -> &'static [&'static str]

Returns the list of config keys whose deserializer accepts more than one TOML type (e.g. either a scalar or a list). The schema is built from a serialized default that can only encode one variant, so the validator would reject the alternative form. The registry replaces the schema entry for each listed key with a polymorphic sentinel so type checking is skipped while the key name is still validated. Keep default_config_section() returning clean defaults — the sentinel is a schema concern and must not leak into user-facing output like rumdl config --defaults.

fn fix_capability(&self) -> FixCapability

Declares the fix capability of this rule

fn cross_file_scope(&self) -> CrossFileScope

Declares cross-file analysis requirements for this rule

fn contribute_to_index( &self, _ctx: &LintContext<'_>, _file_index: &mut FileIndex, )

Contribute data to the workspace index during linting

fn cross_file_check( &self, _file_path: &Path, _file_index: &FileIndex, _workspace_index: &WorkspaceIndex, ) -> LintResult

Perform cross-file validation after all files have been linted