Fix: Ensure correct hexadecimal representation for .toString('hex') and .toString(16) methods #61
Conversation
This file contains 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
|
Hey, thanks for your PR this looks good! |
- Check if the argument is a string representation for the base. - Set base to 16 if the argument is "hex".
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.
Fixes #60
Root Cause
The original implementation of the toString method was designed to only handle numerical base representations. When a string-based representation like
'hex'was passed to the method, it was not recognized or processed, and the method defaulted to returning the decimal string representation of the number (base = 10)Summary:
.toString('hex')and.toString(16)return the expected hexadecimal format of the number.