Skip to content

Punctuate the three bech32 error strings the reader actually sees - #16

Merged
hotpixelgroup merged 1 commit into
mainfrom
bech32-error-strings
Aug 26, 2026
Merged

hotpixelgroup merged 1 commit into
mainfrom
bech32-error-strings

Conversation

@hotpixelgroup

Copy link
Copy Markdown
Owner

These aren't comments. They render on both sites, and two of them appear in the Lightning invoice decoder when a reader breaks an invoice on purpose, which is the whole point of that control.

Colons rather than dashes, matching the pattern the rest of the file already uses for its errors (Too long:, No separator:). Tests assert only the Mixed case substring, so nothing depended on the punctuation.

Everything else in bitcoin-logic stays exactly as it was.

147 tests green; lint, build, typecheck clean.

🤖 Generated with Claude Code

These are not comments. They render on both sites: two of them appear in
the Lightning invoice decoder when a reader breaks an invoice on purpose,
which is the whole point of that control.

Colons rather than dashes, matching the pattern the rest of the file
already uses for its errors ("Too long:", "No separator:"). The tests
assert only the "Mixed case" substring, so nothing depended on the
punctuation.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@hotpixelgroup
hotpixelgroup merged commit 3c22f8d into main Aug 26, 2026
1 check passed
@hotpixelgroup
hotpixelgroup deleted the bech32-error-strings branch August 26, 2026 22:42
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.

1 participant