fix: throw error instead of warning for test-only function in production#335
Open
zkasuran wants to merge 1 commit into
Open
fix: throw error instead of warning for test-only function in production#335zkasuran wants to merge 1 commit into
zkasuran wants to merge 1 commit into
Conversation
Changes createSpendPermissionTypedDataWithSeconds production guard from
soft console.warn to hard throw.
## Problem
Current guard uses console.warn which is invisible to end-users and
silently swallowed by logging pipelines. Function continues execution
and returns valid SpendPermissionTypedData that can be signed and
submitted on-chain in production.
## Risk
Spend permissions authorize recurring token withdrawals. Test utility
with arbitrary second-level periods could be used (accidentally or
intentionally) in production, creating permissions with very short
periods that drain allowances rapidly and are not supported by
production UX.
## Solution
Replace console.warn with throw Error:
```ts
if (process.env.NODE_ENV === 'production') {
throw new Error(
'createSpendPermissionTypedDataWithSeconds is for testing only...'
);
}
```
## Impact
- Production callers fail fast and loudly
- Prevents accidental misuse in production
- Aligns with @testonly JSDoc annotation intent
- No breaking change for correct usage (test-only)
Fixes base#325
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collaborator
🟡 Heimdall Review Status
|
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.
Summary
Changes
createSpendPermissionTypedDataWithSecondsproduction guard from softconsole.warnto hardthrow.Problem (Issue #325)
Current production guard is ineffective:
Issues:
console.warnis invisible to end-usersSecurity Risk
Spend permissions authorize recurring token withdrawals from user accounts. This test utility creates permissions with arbitrary second-level periods (not day-level like production).
Attack scenarios:
Solution
Replace with hard error:
Impact
✅ Production callers fail fast and loudly
✅ Prevents accidental misuse
✅ Aligns with
@testOnlyJSDoc intent✅ No breaking change for correct usage (test-only)
Testing
@testOnlyin JSDocFixes #325