Skip to content

docs(S2): say docstrings and comments plainly - #285

Merged
Flix6x merged 3 commits into
dev/s2-frbc-completefrom
docs/s2-comments-legible
Nov 8, 2026
Merged

Flix6x merged 3 commits into
dev/s2-frbc-completefrom
docs/s2-comments-legible

Conversation

@Flix6x

@Flix6x Flix6x commented Nov 8, 2026

Copy link
Copy Markdown
Member

Into the integration branch dev/s2-frbc-complete (#279), not main.

Answers the review comment on #278 that sentence constructions reduce legibility, and that the problem is widespread. #283 did the changelogs; this does the docstrings and comments.

Scope: every docstring and comment block that the S2 work added or changed (git diff main... over src), rewritten as a whole wherever any line of it changed. About 235 across 16 files. Text outside the diff is left alone.

What changed:

  • Each one leads with what the code does, or why.
  • One idea per sentence, in plain word order. Stacked "which … which" and "as … as" clauses, dangling "included", and figurative "answers", "says so" and "goes out" are gone.
  • Every fact, condition, unit and caveat is kept. Lines still break only after punctuation.

Checks:

  • Only text changed: each touched file parses to the same AST once docstrings are set aside.
  • Faithfulness: an independent read of every rewrite against the text it replaced and the code next to it. It found one false claim (that a failure was always retried before retries were bounded; there were no retries at all), a capacity comment that read as community-level rather than per member site, and a few smaller shifts. All are fixed in the second commit.
  • Tests and hooks: 761 tests pass, and pre-commit is clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CcpawsJs74cSwFLXkz7ZwW

Flix6x and others added 3 commits November 8, 2026 15:48
Rewrite the docstrings and comments that the S2 work added or changed,
so that each one leads with what the code does or why,
in short sentences with plain word order.
Every fact, condition, unit and caveat is kept.
Only text changed: each touched file parses to the same AST once docstrings are set aside.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CcpawsJs74cSwFLXkz7ZwW
Signed-off-by: F.N. Claessen <claessen@seita.nl>
A check of every rewritten docstring and comment against the code found
one false claim (that a failure was always retried before retries were
bounded, when there were no retries at all), a capacity comment that read
as a community-level capacity rather than each member site's, and smaller
shifts: a condition made of a fact, a lost "because", a lost example, a
tense slip, a softened "cannot", and a line over the length limit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CcpawsJs74cSwFLXkz7ZwW
Signed-off-by: F.N. Claessen <claessen@seita.nl>
@Flix6x Flix6x added this to the 0.10.0 milestone Nov 8, 2026
@Flix6x Flix6x added the S2 label Nov 8, 2026
@Flix6x
Flix6x merged commit a2fa1b8 into dev/s2-frbc-complete Nov 8, 2026
20 of 21 checks passed
@Flix6x
Flix6x deleted the docs/s2-comments-legible branch November 8, 2026 14:57
@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 42492174988

Warning

No base build found for commit 4816024 on dev/s2-frbc-complete.
Coverage changes can't be calculated without a base build.
If a base build is processing, this comment will update automatically when it completes.

Coverage: 95.932%

Details

  • Patch coverage: 1 of 1 lines across 1 file are fully covered (100%).

Uncovered Changes

No uncovered changes found.

Coverage Regressions

Requires a base build to compare against. How to fix this →


Coverage Stats

Coverage Status
Relevant Lines: 3171
Covered Lines: 3042
Line Coverage: 95.93%
Coverage Strength: 4.58 hits per line

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants