ErisLint
Rules are declared as typed choices over compiler-like Rust contexts, so teams can tailor checks while dry-run exposes the exact planned state and request before the API call.
Added to Jevfast
How it uses Jev
ErisLint evaluates configurable Rust lint rules with Jev Choice questions. It parses Rust targets, selects matching enabled rules, groups questions by their configured input context, and sends each group the corresponding syntax/source state plus file path. Jev’s selected choice answers become lint findings/recommendations in the report.
What Jev decides
Function simplicity ruleExample answers · not a recorded Jev response · Source ↗
Question 1 · function-simplicity
YOUR APP
INSTRUCTION
Is this Rust function appropriately simple for its purpose? Judge avoidable complexity, not length alone.
STATE
Context-specific Rust function input from target.input(context, source), with relative file path added. The documented starter rule uses id function-simplicity and selects function targets with bodies.
JEV · CHOICE
- simple
- needlessly_complex
- insufficient_context
App workflow
- Load rule configuration
Read rule definitions, selectors, filters, context and diagnostic policy.
- Parse and select targets
Extract configured Rust declaration kinds and match rules by kind, optional body requirement, file filter and enabled setting.
- Build request plan
Group matching rule questions by input context and create one request per context for the target.
- Evaluate and report
Unless dry-run is selected, call Jev and turn typed answers into a report/diagnostics.
Why it is interesting
Rules are declared as typed choices over compiler-like Rust contexts, so teams can tailor checks while dry-run exposes the exact planned state and request before the API call.