On this page:
Dover:   Documentation Coverage
9.3

Dover: Documentation Coverage🔗ℹ

Joel Dueck

Racket has an amazing documentation system in Scribble, and if you’re making Racket packages, you should use it.

Dover checks a set of one or more packages and scores them on how many of their exported bindings have Scribble documentation. Use it from the command line while you write docs, or in CI to keep coverage from slipping.

Installation:

  raco pkg install dover

To use:

  raco dover check ‹options› ‹pkg› ...

Dover reads the documentation that is already installed, so a package’s docs must be built (normally by raco pkg install or raco setup) before Dover can see them.

The canonical copy of this documentation is at https://joeldueck.com/what-about/dover.

    1 Quick tour

    2 Checking a package

      2.1 raco dover check

      2.2 Which modules are checked

      2.3 Which bindings count

      2.4 Where bindings are reported

      2.5 Documentation warnings

      2.6 Configuration in "info.rkt"

        2.6.1 Configuration in split lib/doc packages

      2.7 Using Dover in CI

    3 A recipe for package docs

      3.1 Step 1: Require your modules for-label

      3.2 Step 2: Start a section for each module

      3.3 Step 3: Document functions with defproc

      3.4 Step 4: Document macros with defform

      3.5 Step 5: Build and check

      3.6 When modules re-export each other

      3.7 When public modules share a private module

    4 Library

    5 Acknowledgements