chore: use consistent NoiseStream imports
#862
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 is a types-only change. We import the `NoiseStream` type in a bunch of places. Typically, we import it from the source: `@hyperswarm/secret-stream`. This fixes one occurrence of a spot where we *didn't* do that, and we exporting it via a types utility file.
EvanHahn
force-pushed
the
use-consistent-noisestream-imports
branch
from
f24b936
to
5df95eb
Compare
gmaclennan
approved these changes
Oct 2, 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 is a types-only change.
We import the
NoiseStreamtype in a bunch of places. Typically, we import it from the source:@hyperswarm/secret-stream. This fixes one occurrence of a spot where we didn't do that, and we exporting it via a types utility file.