Component

Forge

Describe the feature you would like

Issue

Currently, when installing a specific version/branch of a dependency, this version is lost when running forge update.
Example:

forge install rari-capital/solmate@v7
forge update

=> checks out to master
I would expect the checked out branch to remain the same.

Example Scenario

I currently am depending on

deploying libraries can take a long time. One can easily skip this stage if we make it possible to save the deployed library state and pass it to dapp test:

1. Write a new little dapp helper script which is the dapp --library-addresses above
2. Make dapp build and dapp --make-library-state use this helper script instead
3. Allow a flag --state to be passed to dapp test (probably a

We should apply sorting to the list of installed apps in the App Center (we "randomize" the discovery page to make it a bit more "fun"):

1. Upgrades available ahead of up to date apps
2. Alphabetical

cc @bpierre @dizzypaty I've also been wondering if it might be nice to start having sections in the App Center similar to Voting, for the different classes of apps (e.g. "ready" vs. "experiment

Some file is importing something from some test file. This means that we have to include the test directory in the published package, but besides that it's just a bad idea. I haven't looked into it, but it's probably easy to fix.

walletconnect always goes to rinkeby...

<UseWalletProvider
chainId={3}
connectors={{
walletconnect: {
rpcUrl:
'https://ropsten.infura.io/v3/7082b757ec2e4ebd8d47ca9518743623',
},
}}
>
...

onConnect={() => connect('walletconnect')}

But...

Response :
POST https://rinkeby.infura.io/v3/ 401 (Unauthorized