Allow setting custom peers when initializing the node#63
Merged
Conversation
thunderbiscuit
force-pushed
the
feat/custom-peers
branch
from
July 16, 2026 14:53
9e09b8d to
ac0a576
Compare
thunderbiscuit
force-pushed
the
feat/custom-peers
branch
from
July 16, 2026 15:21
ac0a576 to
475099e
Compare
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
1 participant
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 PR allows the user to set a custom peer on startup. It also updates the viewmodel pattern to use StateFlow instead of the Compose-native mutable state (just my preference and I believe best practice).