tschm / pytest-alembic / 33149187912

100%

main: 100%

push

github

docs: record why MigrationContext is one class, not two.

`runner.py` is the largest module in the package (521 lines) and has the highest
in-degree in the import graph, and `MigrationContext` holds both the migration verbs and
the history/state accessors. Read as a class in isolation that is two responsibilities
and an obvious split, which is why it keeps being raised.

It is one class because it is the documented public surface -- the object `alembic_runner`
yields, and the receiver of every call in every documented example -- so a split is an
API break rather than a refactor, and the metrics give no reason to want one (no block
above `B`, maintainability index `A`). This records that, and points a future split at
delegation behind the existing public names.

Comment rather than docstring deliberately: the audience is the next person to propose
the split, not the user reading the rendered API page.

Closes #249.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

196 of 196 branches covered (100.0%)

Branch coverage included in aggregate %.

885 of 885 relevant lines covered (100.0%)

7.95 hits per line