Triple backticks can be legitimately used to show single backticks to readers.

Author: JulienPalard

sphinxlint.py

@@ -402,12 +402,16 @@ def type_of_explicit_markup(line):
 )
 
 
-@checker(".rst", severity=2)
+@checker(".rst", falsepositives=True, severity=2)
 def check_triple_backticks(file, lines):
-    f"""Check for triple backticks.
+    """Check for triple backticks.
 
     Good: ``Point``
     Bad: ```Point```
+
+    But in reality, triple backticks are valid: ```foo``` gets
+    rendered as `foo`, it's at least used by Sphinx to document rst
+    syntax, but it's really uncommon.
     """
     for lno, line in enumerate(lines):
         match = triple_backticks.search(line)

tests/fixtures/xfail/triple-backticks.rst …gers-false-positive/triple-backticks.rsttests/fixtures/xfail/triple-backticks.rst renamed to tests/fixtures/triggers-false-positive/triple-backticks.rst tests/fixtures/xfail/triple-backticks.rst renamed to tests/fixtures/triggers-false-positive/triple-backticks.rst

@@ -19,6 +19,28 @@ def test_sphinxlint_shall_pass(file, capsys):
     assert error_count == 0
 
 
+@pytest.mark.parametrize(
+    "file", [str(f) for f in (FIXTURE_DIR / "triggers-false-positive").iterdir()]
+)
+def test_sphinxlint_shall_trigger_false_positive(file, capsys):
+    try:
+        main(["sphinxlint.py", str(file)])
+    except SystemExit as err:
+        error_count = err.code
+    out, err = capsys.readouterr()
+    assert out == "No problems found.\n"
+    assert err == ""
+    assert error_count == 0
+    try:
+        main(["sphinxlint.py", "-f", str(file)])
+    except SystemExit as err:
+        error_count = err.code
+    out, err = capsys.readouterr()
+    assert out != "No problems found.\n"
+    assert err == ""
+    assert error_count > 0
+
+
 @pytest.mark.parametrize("file", [str(f) for f in (FIXTURE_DIR / "xfail").iterdir()])
 def test_sphinxlint_shall_not_pass(file, capsys):
     try: