initial fetch profile w/ nostr-react, show profile in navbar #18
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
✅ Deploy Preview for superlative-biscotti-9be5a4 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Also I removed the |
|
Another problem with nostr-react is that it kinda locks us into a fixed set of relays for subscribing + publishing. |
|
think i broke this need to fix it still |
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.
Initial implementation of #11, using
nostr-reactpackage.Nostr-react useProfile implementation doesn't return last updated profile metadata... instead it returns the latest event received (can cause flashing). See t4t5/nostr-react#17
I also added prettierignore b/c my editor keeps changing everything lol my bad