rigsql_rules/convention/
cv11.rs

1use rigsql_core::SegmentType;
2
3use crate::rule::{CrawlType, Rule, RuleContext, RuleGroup};
4use crate::violation::LintViolation;
5
6/// CV11: Use of BETWEEN operator.
7///
8/// The BETWEEN operator can be confusing, especially with date ranges,
9/// because it is inclusive on both ends. Prefer explicit >= AND <= comparisons.
10#[derive(Debug, Default)]
11pub struct RuleCV11;
12
13impl Rule for RuleCV11 {
14    fn code(&self) -> &'static str {
15        "CV11"
16    }
17    fn name(&self) -> &'static str {
18        "convention.no_between"
19    }
20    fn description(&self) -> &'static str {
21        "Use of BETWEEN operator."
22    }
23    fn explanation(&self) -> &'static str {
24        "The BETWEEN operator is inclusive on both ends and can lead to subtle bugs, \
25         especially with date/time ranges. For example, 'BETWEEN '2024-01-01' AND '2024-01-31'' \
26         may miss times on the 31st after midnight. Prefer explicit '>= ... AND <= ...' for clarity."
27    }
28    fn groups(&self) -> &[RuleGroup] {
29        &[RuleGroup::Convention]
30    }
31    fn is_fixable(&self) -> bool {
32        false
33    }
34
35    fn crawl_type(&self) -> CrawlType {
36        CrawlType::Segment(vec![SegmentType::BetweenExpression])
37    }
38
39    fn eval(&self, ctx: &RuleContext) -> Vec<LintViolation> {
40        vec![LintViolation::new(
41            self.code(),
42            "Use of BETWEEN. Consider using >= and <= for explicit range boundaries.",
43            ctx.segment.span(),
44        )]
45    }
46}
rigsql_rules/convention/cv11.rs

rigsql_rules/convention/
cv11.rs
