fix: more consistent panic strings #678
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #678 +/- ##
=======================================
Coverage 94.49% 94.49%
=======================================
Files 18 18
Lines 3305 3305
=======================================
Hits 3123 3123
Misses 170 170
Partials 12 12
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
samber
reviewed
Sep 24, 2025
Owner
samber
left a comment
There was a problem hiding this comment.
Hey @NathanBaulch
Thanks for this fix. Just a little comment ;)
.github/workflows/lint.yml
Outdated
Updated golangci-lint action version to v2.4.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed some inconsistencies in panic strings during my work on #672. I went with the pattern used in
lo.RandomStringando.ChunkStringwith the function name prefix and lower case message. I don't mind what convention is used as long as it's consistent.Note that I haven't touched the panics returned from
Mustwhich use a "must: " prefix in lowercase, since consumers might have recover logic that inspects this relatively common panic message.