This tackles the long outstanding #63 without using the Loopring API but with some graphQL trickery:
It builds its own never expiring cache (since the information cannot change really).
It has to make some assumptions (e.g. decimal places of pool tokens) but AFAICS these should all be okay.
Some of this - but not everything - would have been easier with the token list from the Loopring API (and of course with an improved graph none of this would have been necessary), but I am actually quite fine with the way this turned out.
@fudgebucket27 and @danielsolistensvik I'd love to hear your take on this!
This tackles the long outstanding #63 without using the Loopring API but with some graphQL trickery:
@fudgebucket27 and @danielsolistensvik I'd love to hear your take on this!