You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Livepeer reported that their contracts BondingManager and RoundsManager share some types, causing a name conflict when the ABIs of both contracts are added to a same mapping. The best solution would be to namespace the types by contract, but in this case since the types are equal de-duplicating would suffice.
The text was updated successfully, but these errors were encountered:
Prefixing would generate long, not very user-friendly type names. I wonder if we could make it so that users can import the types they want selectively, e.g. with
Livepeer reported that their contracts
BondingManager
andRoundsManager
share some types, causing a name conflict when the ABIs of both contracts are added to a same mapping. The best solution would be to namespace the types by contract, but in this case since the types are equal de-duplicating would suffice.The text was updated successfully, but these errors were encountered: