Open sakulstra opened 5 months ago
It probably would be best to instead normalize naming so that imports are consistent.
@pegahcarter it's not really possible in a reasonable way.
In practice accessing Pool.Asset.UNDERLYING
(how it is on ts part of the library) would be more comfortable then Pool.Asset_UNDERLYING
. Originally we replicated a similar behavior in solidity via Pool.Asset().Underlying()
, but this has code-size and compile-time implications which were not worth the tradeoff.
On js side, it's quite nice to be able to just iterate over the objects, so eventually it's a tradeoff we settled on.
Would be nice if selecting/hovering an item, would show how to actually use it in code via address-book. This can be useful especially as imports are wildly different on solc vs js: