Skip to content

Stop documenting consecutive declarations#348

Merged
fingolfin merged 1 commit intomasterfrom
codex/fix-169-consecutive-declarations
Mar 12, 2026
Merged

Stop documenting consecutive declarations#348
fingolfin merged 1 commit intomasterfrom
codex/fix-169-consecutive-declarations

Conversation

@fingolfin
Copy link
Member

@fingolfin fingolfin commented Mar 12, 2026

Stop carrying declaration-scan state past the first declaration
after an AutoDoc source comment block. This makes declaration
documentation match the documented immediate-adjacency rule
instead of implicitly attaching the same comment block to later
consecutive declarations.

Add a regression test for consecutive declarations and make the
general worksheet fixture spell out the later category
declarations explicitly so it no longer depends on the old buggy
behavior.

AI-assisted with Codex for implementation, test updates, and
changelog entry.

Fixes #169

Co-authored-by: Codex codex@openai.com

@codecov
Copy link

codecov bot commented Mar 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.79%. Comparing base (1c390d5) to head (8bdde58).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #348   +/-   ##
=======================================
  Coverage   91.79%   91.79%           
=======================================
  Files          13       13           
  Lines        2609     2609           
=======================================
  Hits         2395     2395           
  Misses        214      214           
Files with missing lines Coverage Δ
gap/Parser.gi 96.42% <100.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@fingolfin fingolfin changed the title codex/fix 169 consecutive declarations Stop documenting consecutive declarations Mar 12, 2026
Stop carrying declaration-scan state past the first declaration
after an AutoDoc source comment block. This makes declaration
documentation match the documented immediate-adjacency rule
instead of implicitly attaching the same comment block to later
consecutive declarations.

Add a regression test for consecutive declarations and make the
general worksheet fixture spell out the later category
declarations explicitly so it no longer depends on the old buggy
behavior.

AI-assisted with Codex for implementation, test updates, and
changelog entry.

Fixes #169

Co-authored-by: Codex <codex@openai.com>
@fingolfin fingolfin force-pushed the codex/fix-169-consecutive-declarations branch from 1dfcb07 to 8bdde58 Compare March 12, 2026 21:33
@fingolfin fingolfin enabled auto-merge (squash) March 12, 2026 21:33
@fingolfin fingolfin merged commit 637e8bc into master Mar 12, 2026
8 checks passed
@fingolfin fingolfin deleted the codex/fix-169-consecutive-declarations branch March 12, 2026 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Question: intention with respect to consecutive declarations?

1 participant