fix: export DHT record class #2168
Merged
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
This needs to be exported for reuse by things that create DHT records such as IPNS. Exported as `Record` because it's a KAD-DHT specific record and `KAD-DHT` in a class name is redundant within the scope of the KAD-DHT module.
wemeetagain
approved these changes
Oct 24, 2023
This was referenced Jan 18, 2024
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.
This needs to be exported for reuse by things that create DHT records such as IPNS. Previously it was imported from the
@libp2p/recordmodule.Exported as
Recordbecause it's a KAD-DHT specific record andKAD-DHTin a class name is redundant within the scope of the KAD-DHT module.Change checklist