Opinionated OCaml linter with Merlin integration for code quality, naming conventions, and style checks
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

merlint: add cram test for E835 (pip --break-system-packages)

+56
+1
test/cram/e835.t/bad/dune-project
··· 1 + (lang dune 3.21)
+2
test/cram/e835.t/bad/foo/test/interop/oracle/scripts/generate.sh
··· 1 + #!/bin/sh 2 + pip install --break-system-packages crcmod
+1
test/cram/e835.t/good/dune-project
··· 1 + (lang dune 3.21)
+4
test/cram/e835.t/good/foo/test/interop/oracle/scripts/generate.sh
··· 1 + #!/bin/sh 2 + python3 -m venv .venv 3 + . .venv/bin/activate 4 + pip install -r requirements.txt
+48
test/cram/e835.t/run.t
··· 1 + Test bad example - generate.sh uses pip install --break-system-packages: 2 + $ merlint -B -r E835 bad/ 3 + Running merlint analysis... 4 + 5 + Analyzing 0 files 6 + 7 + ✓ Code Quality (0 total issues) 8 + ✓ Code Style (0 total issues) 9 + ✓ Naming Conventions (0 total issues) 10 + ✓ Documentation (0 total issues) 11 + ✓ Project Structure (0 total issues) 12 + ✓ Test Quality (0 total issues) 13 + ✗ Interop Testing (1 total issues) 14 + [E835] pip install --break-system-packages (1 issue) 15 + Python deps must live in a venv. Never use pip install 16 + --break-system-packages. The generate.sh wrapper should create/reuse a venv 17 + automatically. 18 + - (global) bad/foo/test/interop/oracle/scripts/generate.sh uses --break-system-packages 19 + ✓ Code Generation (0 total issues) 20 + 21 + ╭─────────────────┬───────────────────────────────────────────╮ 22 + │ Category │ Issues │ 23 + ├─────────────────┼───────────────────────────────────────────┤ 24 + │ Interop Testing │ 1 (1 pip install --break-system-packages) │ 25 + ╰─────────────────┴───────────────────────────────────────────╯ 26 + 27 + 28 + Summary: ✗ 1 total issue (applied 1 rule) 29 + ✗ Some checks failed. See details above. 30 + [1] 31 + 32 + Test good example - generate.sh uses a venv: 33 + $ merlint -B -r E835 good/ 34 + Running merlint analysis... 35 + 36 + Analyzing 0 files 37 + 38 + ✓ Code Quality (0 total issues) 39 + ✓ Code Style (0 total issues) 40 + ✓ Naming Conventions (0 total issues) 41 + ✓ Documentation (0 total issues) 42 + ✓ Project Structure (0 total issues) 43 + ✓ Test Quality (0 total issues) 44 + ✓ Interop Testing (0 total issues) 45 + ✓ Code Generation (0 total issues) 46 + 47 + Summary: ✓ 0 total issues (applied 1 rule) 48 + ✓ All checks passed!