Throw error for invalid currency conversion inputs - #1262
Open
pavankumar-vh wants to merge 1 commit into
Open
Conversation
The previous version silently returned 0 when centsPerCredit was invalid or credits/amountInCents was NaN/Infinity. This is dangerous in money-conversion paths because misconfigurations would silently produce wrong values rather than failing loudly. Changed to throw explicit errors with descriptive messages so invalid inputs are caught immediately during development and testing.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
Fix currency conversion functions in
common/src/util/currency.tsto throw errors instead of silently returning 0 for invalid inputs.Bug Description
The previous version silently returned 0 when:
centsPerCreditwas 0 or negative (division by zero or negative rate)creditsoramountInCentswas NaN or InfinityThis is dangerous in money-conversion paths because misconfigurations would silently produce wrong values rather than failing loudly. A bad Stripe price setup or calculation error would result in users getting 0 credits/cents without any indication that something went wrong.
Fix
Changed to throw explicit errors with descriptive messages so invalid inputs are caught immediately during development and testing:
Testing
No existing tests for these functions, but the fix prevents silent failures in production.
Files Changed
common/src/util/currency.ts- Throw errors for invalid inputsScope
This change only touches
common/which is an approved contribution area per the Contributing Guide.