-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cli): add support for outputting .avm and .debug files from @neo-one/cli #2071
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should try to output something better for the id and entrypoint properties. Maybe by looking at what the debugger uses them for and then just creating something to fit that purpose? Idk. We should discuss more over VC.
We should update the compile
e2e test for this too. Which should be very easy. I can do it in a separate PR if you want since I wrote that test originally.
3eb6964
to
82ce408
Compare
Codecov Report
|
01038fd
to
3fccc93
Compare
5cc5a50
to
0aa817c
Compare
Issues
#2002 #2000
Description
Adds several new CLI flags for the
neo-one compile
command. These flags are:--json
- defaults totrue
, outputs a.contract.json
and.neoone.abi.json
.--avm
- defaults tofalse
, outputs the contract bytecode as a.avm
file and a compatible.abi.json
file.--opcodes
- defaults tofalse
, outputs a.avm.txt
of disassembled bytecode from the.avm
file.--debug
- defaults tofalse
, ifjson
is specified outputs the uncompressed.debug.json
. Ifavm
is specified outputs the compressed.avmdbgnfo
.Testing
If you have a contract/neo-one config you can build this and run:
against your test contract(s) with the various flags.
Further Work
While we are able to output
.avm
and.abi
files now there is still some work to be done in integrating with the neo toolkit. See #2113 for more information