Opinionated OCaml linter with Merlin integration for code quality, naming conventions, and style checks
merlint: add cram test for E801 (interop dir named after language)
+50
+1
test/cram/e801.t/bad/dune-project
+1
test/cram/e801.t/bad/dune-project
···
1
+
(lang dune 3.21)
test/cram/e801.t/bad/foo/test/interop/python/.keep
test/cram/e801.t/bad/foo/test/interop/python/.keep
This is a binary file and will not be displayed.
+1
test/cram/e801.t/good/dune-project
+1
test/cram/e801.t/good/dune-project
···
1
+
(lang dune 3.21)
test/cram/e801.t/good/foo/test/interop/spacepackets/.keep
test/cram/e801.t/good/foo/test/interop/spacepackets/.keep
This is a binary file and will not be displayed.
+48
test/cram/e801.t/run.t
+48
test/cram/e801.t/run.t
···
1
+
Test bad example - foo/test/interop/python/ named after language:
2
+
$ merlint -B -r E801 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
+
[E801] Interop dir named after language (1 issue)
15
+
Interop test directories should be named after the oracle tool (e.g.
16
+
spacepackets, dariol83, crcmod), not the language (e.g. python, go). This
17
+
makes it clear which external implementation is the reference.
18
+
- (global) Interop dir bad/foo/test/interop/python: directory named after language "python", should be named after the oracle tool
19
+
✓ Code Generation (0 total issues)
20
+
21
+
╭─────────────────┬────────────────────────────────────────╮
22
+
│ Category │ Issues │
23
+
├─────────────────┼────────────────────────────────────────┤
24
+
│ Interop Testing │ 1 (1 interop dir named after language) │
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 - foo/test/interop/spacepackets/ named after oracle tool:
33
+
$ merlint -B -r E801 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!