Stefan HallerandClaude Opus 5 db6a04b8a5 Add a well-formedness check for a parsed patch ...

Parse is lenient: it takes any text and reads a diff out of it, which is
what we want when we hand it a diff, but it has no way to say "this
isn't one". We're about to parse the *rendered* contents of a diff view,
which a diff renderer is free to restructure — putting the line numbers
in a gutter, say, shifts the +/- marker off the start of each body line,
so every line reads as context and the parse silently lies about which
lines are changes.

Comparing each hunk's body against the lengths its header declares
catches exactly that, without teaching us anything about any particular
renderer's layout: a faithful unified diff agrees with its headers, a
restructured one doesn't.

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

2026-10-04 19:01:01 +02:00

..

format.go

Export PatchLine.isChange

2025-07-04 10:14:35 +02:00

hunk.go

Add a well-formedness check for a parsed patch

2026-10-04 19:01:01 +02:00

parse.go

Add a well-formedness check for a parsed patch

2026-10-04 19:01:01 +02:00

patch_builder.go

Guard the patch builder against concurrent access

2026-07-17 12:35:54 +02:00

patch_line.go

Fix selection after staging an added line

2026-03-19 16:57:53 +01:00

patch_test.go

Add a well-formedness check for a parsed patch

2026-10-04 19:01:01 +02:00

patch.go

Add a well-formedness check for a parsed patch

2026-10-04 19:01:01 +02:00

transform.go

Show renamed files in the custom patch builder

2026-07-04 13:05:09 +02:00