Open tabaktoni opened 9 months ago
Hi @tabaktoni ; Can I work on this issue? I've been reading up on the repo, for some time now. I initially saw it on OnlyDust, and asked @ivpavici if I could work on this one. Looks like no one else has picked this issue yet :D
@ivpavici Thanks for assigning this to me. :D I won't be able to get to it before coming Monday, because of some other obligations 😅 But this is in my list and I'll try to push the relevant changes in a few days.
no worries, take your time!
Is your feature request related to a problem? Please describe. This feature is nice to have as tools could use it and build on it. Currently, we support encoding &. decoding with ABI:
JSC types -> calldata
responsedata -> JSC types
Describe the solution you'd like It would also be nice to have a calldata decoder:
calldata -> JSC types
and api data encoder:JSC types -> responsedata
Internally we do not need such a flow other than maybe adding additional validation options/ testing, but this could helpAdditional context With ABI this would complete a circle of data conversion as so one could do:
calldata -> JSC types -> responsedata
We could improve the test with excepted results for echo test methods