Fix: Fix Object ID decoding logic for uppercase HEX string#274
Merged
zookzook merged 1 commit intozookzook:masterfrom Apr 17, 2025
Merged
Fix: Fix Object ID decoding logic for uppercase HEX string#274zookzook merged 1 commit intozookzook:masterfrom
zookzook merged 1 commit intozookzook:masterfrom
Conversation
Contributor
Author
|
@zookzook can you please take a look? |
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
2 participants
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.
prior tho this change
BSON.ObjectId.decode!/was working incorrectly with uppercase hex strings.It mapped A->0, B->1, C->2...F ->5
Instead of A->10, B->11... F->15