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
Currently if a module is uploaded with --included-artifacts none we cannot get its source code from PackageMetadata, that's why we're not rendering source code in module /code path.
However, with Revela Decompilor https://revela.verichains.io/, we can at least display decompiled source code. This feature is available on both Revela web app and Aptos CLI, though integrating it with aptos explorer would help devs a lot.
Questions:
Do you think it is a worthy add?
Is there an easy way to get the decompiled source code in TypeScript? In the worst case we can call Revela API, but that means slow UI
The text was updated successfully, but these errors were encountered:
I think it could be useful; however, it would probably be a slow UI. It also doesn't support Move 2, so I'm waiting on a decompiler that supports Move 2 before adding any features that may be partially broken.
I think it could be useful; however, it would probably be a slow UI. It also doesn't support Move 2, so I'm waiting on a decompiler that supports Move 2 before adding any features that may be partially broken.
Currently if a module is uploaded with
--included-artifacts none
we cannot get its source code from PackageMetadata, that's why we're not rendering source code in module /code path.However, with Revela Decompilor https://revela.verichains.io/, we can at least display decompiled source code. This feature is available on both Revela web app and Aptos CLI, though integrating it with aptos explorer would help devs a lot.
Questions:
The text was updated successfully, but these errors were encountered: