more options for classes.json

Open nmushegian opened this issue 9 years ago • 2 comments

Allow using more of solc's --combined-json options. Dapple's build output should differ from solc's as little as possible for simple single-file packages

Jun 23 '16 20:06 nmushegian

Ideally, Dapple could support the same output options as solc, for example to provide separate ABI and BIN files for each contract that can be used with other tools. One good example is the native Go binding generator, abigen, as seen here:

https://github.com/ethereum/go-ethereum/wiki/Native-DApps:-Go-bindings-to-Ethereum-contracts

Currently, it's quite problematic to integrate a Dapple smart contract into a Golang project. Not sure what the situation is for bindings in other languages.

Jun 23 '16 20:06 awfm9

@nmushegian @awishformore both of these options are great. This should definitely be an option given the social climate around minimizing unneeded data/requires in the JS community.

Jun 24 '16 15:06 SilentCicero