Moody Salem
Moody Salem
similar to ethtx.info, we want to see what contracts are called and the decoded calldata in the execution transaction of the proposal
running it locally is good, but is manual testing, and checks can break would be good to have some automated tests that verify the results of checks on individual proposals...
p1 - [ ] `ApproveAndCall` for tokens that require ApprovalType.MAX_MINUS_ONE-style approves - [ ] `PeripheryPaymentsExtended` - [ ] `PeripheryPaymentsWithFeeExtended` - [ ] every slippage check - [ ] fee-on-transfer token...
equivalent to these two commits: - https://github.com/Uniswap/uniswap-interface/commit/8d90bb7a3990b8a7f6394969cf89432c7831fec7 - https://github.com/Uniswap/uniswap-interface/commit/bdcb9a8a0ae75327b820b9fb7bb19eceeb9c87c8
https://github.com/Uniswap/v3-info/blob/f8b823ff481da74e52948128401bf5672907e1bd/package.json#L4 this will allow urls like https://info.uniswap.org/optimism/ to work (but won't render optimism route) the interface has a different homepage than app.uniswap.org because it's meant to be hosted on ipfs...
### Problem when i run a single test via `scarb test -f ...` it takes 5-10 seconds just to run i suspect it's re-building all the code just to run...
the static schema does not match the the request type, and does not have typing on the handle parameters makes this library really hard to use it's also not clear...
### Issue I have an enum ```dart enum Thing { ONE, TWO } ``` and I want to present some text based on the enum ```dart thingDisplayText(Thing thing) => Intl.select(thing,...
no visibility into what's happening when this thing doesn't work