A standalone tool beside the library

A library that has an operator's use case ships a standalone command beside it. The command is usable with no knowledge of the library's internals, and the library is usable without the command. The command is the operator's interface; the library is the integrator's. Coupling them forces one audience to carry the other's dependencies.

How the command and the library are laid out

Where the organization applies the principle

The sqlate library established the pattern. Its conventions linter is the sqlint package, callable from a program, and the sqlint command in the same sub-module runs that package over a module for an operator. The sub-module keeps the linter's configuration-file dependency out of the base library.

Keyboard shortcuts

Settings