Sean Casey

@mocolicious Thanks for creating this issue. We're already on it, but it will likely require a core change because of how the claiming functions are implemented. For now, the rewards...

Submitted an AIP to make this possible in Enzyme: https://governance.aave.com/t/proposal-adapt-contracts-slightly-to-improve-defi-composability/4125

Thanks for the issue, will investigate!

Submitted an AIP to make this possible in Enzyme: https://governance.aave.com/t/proposal-adapt-contracts-slightly-to-improve-defi-composability/4125

Update the test app for the react context api with a `LoadingContainer`. We can add the overrides for this component at a later time. The README reflects the new props...

@adrianmcli Did you set `networkWhitelist` in `drizzleOptions`? If the option is absent, it will default to `[]`, which means all networks are approved.

@adrianmcli Sure, I can add a `networkWhitelist` config option with values if that's what you mean. So long as you're sure it won't trip people up to have particular networks...

@adrianmcli How about `[1, 4]` (Mainnet, Rinkeby) for the allowed networks? Then Ropsten etc will catch the network mismatch. Ganache is allowed by default, regardless of the values in the...

The purpose of this PR is to allow the LoadingContainer to work with the `networkWhitelist` option that was merged previously. This blog post details and has links to both that...

Yes, but the idea was to separate out functionality and UI/UX. Rather than assuming UI/UX, we just provide a developer with the `networkMismatch` flag that is produced when the provider...