-
Notifications
You must be signed in to change notification settings - Fork 493
fix: Function to handle BigInt value in JSON.stringify #363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Function to handle BigInt value in JSON.stringify #363
Conversation
nirmal25990
commented
Feb 8, 2024
•
edited
Loading
edited
- BigInt value is not working #362
- This could be a solution for this if we don't want to use any additional library like superjson
@nirmal25990 I'd prefer if we didn't have a custom json stringifier function here. |
this.operator | ||
} ${JSON.stringify(rightHandSideValue)}?> (${result})` | ||
} ${jsonStringifyWithBigInt(rightHandSideValue)}?> (${result})` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's avoid a custom stringifier here when we can instead rely on the console.log
built-in formatter if we change the signature of debug
Change the call signature, leverage built-in formatting on console. Move debug enablement checks to file load. Replaces CacheControl#363 Resolves CacheControl#362 Co-Author Nirmal Patel <nirmal259907@gmail.com>
Change the call signature, leverage built-in formatting on console. Move debug enablement checks to file load. Replaces CacheControl#363 Resolves CacheControl#362 Co-Author Nirmal Patel <nirmal259907@gmail.com>
Replaced by #378 |
Change the call signature, leverage built-in formatting on console. Move debug enablement checks to file load. Replaces CacheControl#363 Resolves CacheControl#362 Co-Author Nirmal Patel <nirmal259907@gmail.com>