Skip to content

Commit 64879db

Browse files
claudeclaude
committed
Close a docstring the merge left truncated
Resolving the conflict in features/post.feature dropped the closing '\"\"\"' and the blank line after it from main's last scenario in that hunk, folding its final assertion into the next scenario's step text. python's regex split landed one line short of the boundary because that scenario's own content ended in a '\"\"\"' line with nothing after it to anchor on. Caught by parsing every changed feature file with Gherkin's own parser directly, rather than trusting a line-count or brace-balance heuristic - the malformed steps were still syntactically paired '\"\"\"' markers, just attached to the wrong content, so a diff would have looked plausible. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014SSZzqMJRDTiLiDxQEPYcL
1 parent 7b4f13c commit 64879db

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

‎features/post.feature‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -877,6 +877,7 @@ Feature: Manage WordPress posts
877877
Then STDOUT should be:
878878
"""
879879
2
880+
"""
880881

881882
Scenario: Set a post's modification date on update
882883
Given a WP install

0 commit comments

Comments
 (0)