fix: In ListUsersByPrefix, pass the address of the tree to ListByteStringKeysByPrefix #147
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
…stByteStringKeysByPrefix. See the PR Signed-off-by: Jeff Thompson <[email protected]>
D4ryl00
approved these changes
Dec 20, 2024
jefft0
deleted the
fix/pass-tree-address-to-ListByteStringKeysByPrefix
branch
|
🎉 This PR is included in version 1.11.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
A recent gno PR has a breaking change to make
ListByteStringKeysByPrefixuse the newavl.ITreeinterface. As shown in that PR's update to users.go, it's necessary to pass the address of the tree when callingListByteStringKeysByPrefix. This PR does the same thing in dsocial.