Add support for custom networks #423
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
serjonya-trili
force-pushed
the
add-support-for-custom-networks
branch
from
f2cb83e
to
69758eb
Compare
ryutamago
reviewed
Sep 7, 2023
serjonya-trili
force-pushed
the
add-support-for-custom-networks
branch
from
69758eb
to
f6133b0
Compare
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.
Proposed changes
Task link
networks are now stored in a separate slice (not assetsSlice yey)
network change doesn't reset assetsSlice, will be addressed separately
TezosNetwork was converted from a string enum to a Network config with all the necessary urls included
Types of changes
Steps to reproduce
You can manually add one network to localstorage
Screenshots
Screen.Recording.2023-09-06.at.14.51.15.mov
Checklist