This repository has been archived by the owner on Feb 23, 2024. It is now read-only.
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.
chore: restructure App
Moves routes to a separate file for better visibility.
chore: suffix page components with "Page"
I think we should generally be more explicit in naming. It's very probable that we have things like
class UserModel
,function UserView
orfunction UserPage
which would clash if we named all of themUser
.chore: add Recoil
Added Recoil for managing the UI state. There's also a
persistEffect
Recoil effect that will persist atoms to LocalStorage. (Used this to store wallet PK.)Note: I'm not saying we should use Recoil to store data. I'm mainly thinking of things like:
chore: rename WalletContext to AppContext and add useContract
Heavily refactored this.
useWallet
is now calleduseAppContext
and not used that much. There are two new hooks:useWallet
: just returns the Wallet in the context, not the whole context as it used to.useContract
: returns the main SwaySwap contract with the wallet connected to it.chore: lazy load pages
Now, code for only necessary pages will be loaded.
chore: upgrade React to 18.1.0