line_endings

Every line ending matches target: lf or crlf. Mixed endings in a single file fail.

Options

Option	Type	Required	Default	Description
target	one of lf | crlf	yes		Required line ending style: lf or crlf. Mixed endings within a file also fail.

Plus the common paths, level, id, when, and expect_matches fields. This table is generated from the JSON Schema; option types and defaults are authoritative.

Example

A source file with CRLF line endings under an LF policy

The rule fires on this repository:

• src/
• src/has_crlf.rs✗

  ✗ error lf-only

  1:1 line 1 does not use lf line endings

• src/pure_lf.rs✓

src/has_crlf.rs

fn c() {}<U+000D>
fn d() {}

src/pure_lf.rs

fn a() {}
fn b() {}

With this .alint.yml:

version: 1
rules:
  - id: lf-only
    kind: line_endings
    paths: "src/**/*.rs"
    target: lf
    level: error

alint check reports:

--- src/has_crlf.rs ------------------------------------------------------------
  x  error    lf-only
              1:1  line 1 does not use lf line endings

Summary (1 violation):
  x 1 error
  0 passing * 1 failing

Every source file uses LF line endings

This repository is compliant:

• src/
• src/a.rs✓
• src/b.rs✓

src/a.rs

fn a() {}
fn b() {}

src/b.rs

fn c() {}

With this .alint.yml:

version: 1
rules:
  - id: lf-only
    kind: line_endings
    paths: "src/**/*.rs"
    target: lf
    level: error

alint check reports:

v All 1 rule(s) passed.