dapp

blocked by (at least) typescript-eslint/typescript-eslint#4471

Component

Forge

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

forge 0.1.0 (67f9ed1 2022-02-23T00:44:43.196862+00:00)

What command(s) is the bug in?

forge flatten

Operating System

macOS (amd)

Describe the bug

When flattening a contract the license is formatted in a weird

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

I left a review and then got this message

which seems strange as it's telling me something I know.

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

Expected behavior

If a user, who does not have any remaining ODIS quota, sends a previously sent request to ODIS, they should receive a response as it does not cost quota to replay a request.

Current behavior

Currently the check that a request is replay occurs after the check that a user has positive quota. As a result, replays sent by a user with 0 quota will be rejected.

https: