declint-core 1.3.0

Config and regex linting engine for declint: YAML rule files, message templates, violations. No LSP dependencies.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62

# declint preset: JSON
#
# A curated starter ruleset for JSON. Import it:
#
#   import:
#     - preset:json
#
# Assumes pretty-printed JSON (one key per line). Single-line minified
# files will over-report on some rules.

version: 1

rules:
  # Trailing commas are the most common JSON syntax error.
  - id: trailing-comma
    pattern: ',\s*[}\]]'
    message: "trailing comma — JSON does not allow one before } or ]"
    severity: error
    tests:
      - name: trailing comma is flagged
        text: "{ \"a\": 1, }\n"
        violations: 1
      - name: normal comma passes
        text: "{ \"a\": 1, \"b\": 2 }\n"
        violations: 0

  - id: single-quoted-string
    pattern: "'[^']*'\\s*:"
    message: "JSON requires double-quoted keys"
    severity: error
    tests:
      - name: single-quoted key is flagged
        text: "{ 'a': 1 }\n"
        violations: 1
      - name: double-quoted key passes
        text: "{ \"a\": 1 }\n"
        violations: 0

  - id: unquoted-key
    pattern: '(?m)^\s*[A-Za-z_]\w*\s*:'
    message: "JSON keys must be double-quoted strings"
    severity: error
    tests:
      - name: unquoted key is flagged
        text: "{ a: 1 }\n"
        violations: 1
      - name: quoted key passes
        text: "{ \"a\": 1 }\n"
        violations: 0

  # JSON has no comment syntax — these lines are syntax errors.
  - id: json-comments
    pattern: '//'
    message: "JSON has no comments — remove or move to documentation"
    severity: error
    tests:
      - name: comment is flagged
        text: "{ \"a\": 1 } // note\n"
        violations: 1
      - name: comment-free file passes
        text: "{ \"a\": 1 }\n"
        violations: 0