Skip to content

billing.rb: destroy -> destroy!#2508

Merged
jorgemanrubia merged 1 commit intobasecamp:mainfrom
henrik:patch-1
Mar 3, 2026
Merged

billing.rb: destroy -> destroy!#2508
jorgemanrubia merged 1 commit intobasecamp:mainfrom
henrik:patch-1

Conversation

@henrik
Copy link
Contributor

@henrik henrik commented Feb 8, 2026

Don't have much context but from a quick look, there's no intentional "silently fail to destroy" path here.

@henrik
Copy link
Contributor Author

henrik commented Feb 8, 2026

There are a bunch more destroy where the return value is ignored. I'm guessing most should ideally be destroy!.

@jorgemanrubia
Copy link
Member

Thanks @henrik, you are right we should be leaning towards destroy! in other places too

@jorgemanrubia jorgemanrubia merged commit f695218 into basecamp:main Mar 3, 2026
4 of 5 checks passed
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.

2 participants