Define RST218 Literal block expected; none found.

Author: peterjc

README.rst

@@ -105,6 +105,7 @@ RST214 Inline literal start-string without end-string.
 RST215 Inline interpreted text or phrase reference start-string without end-string.
 RST216 Multiple roles in interpreted text (both prefix and suffix present; only one allowed).
 RST217 Mismatch: both interpreted text role suffix and reference suffix.
+RST218 Literal block expected; none found.
 RST299 Previously unseen warning, not yet assigned a unique code.
 ====== =======================================================================
 
@@ -218,6 +219,7 @@ Version History
 ======= ========== ===========================================================
 Version Released   Changes
 ------- ---------- -----------------------------------------------------------
+v0.0.13 2019-12-26 - Adds ``RST218``.
 v0.0.12 2019-11-18 - Adds ``RST213`` to ``RST217``.
 v0.0.11 2019-08-07 - Configuration options to define additional directives and
                      roles (e.g. from Sphinx) for ``RST303`` and ``RST304``.

flake8_rst_docstrings.py

@@ -176,6 +176,7 @@ def tokenize_open(filename):
     "Inline interpreted text or phrase reference start-string without end-string.": 15,
     "Multiple roles in interpreted text (both prefix and suffix present; only one allowed).": 16,  # noqa: E501
     "Mismatch: both interpreted text role suffix and reference suffix.": 17,
+    "Literal block expected; none found.": 18,
 }
 
 # Level 3 - error

tests/RST218/no_literal_block.py

@@ -0,0 +1,15 @@
+"""Print 'Hello world' to the terminal.
+
+RST uses double colons to indicate the following
+indented text is a literal block. The following
+code snippet is a typical usage::
+
+    $ flake8 --select RST RST218/no_literal_block.py
+    RST218/no_literal_block.py:14:1: RST218 Literal block expected; none found.
+
+This file triggers an error because this paragraph
+says there should be a following literal block, but
+there is none::
+"""
+
+print("Hello world")