feat(transport): simplify NostrSigner initialization to accept hex string#47
Merged
ContextVM-org merged 1 commit intoApr 21, 2026
Conversation
3e4d632 to
ff14ced
Compare
Contributor
Author
|
Tests are passing now |
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
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 #46
Description
This PR addresses the TODO in
base-nostr-transport.tsby improving the ergonomics of theNostrSignerinitialization. It allows thesigneroption to directly accept a hex-encoded private key string as a shorthand, automatically wrapping it in aPrivateKeySignerinternally.This is a non-breaking, additive change. Existing code that passes a completely instantiated
NostrSignerwill continue to function exactly as before.Changes Made
BaseNostrTransportOptions.signerto acceptNostrSigner | string.PrivateKeySigner.stringandNostrSignerinputs.Testing Performed
tsc --noEmit) - passed.