sol! tracking issue

[DaniPopes]

This is a tracking issue for missing sol! proc macro (and corresponding sol-types, syn-solidity) features.

Blockers

• feat: syn-solidity visitors #68
• Add support for events #38
• Add sol! support for contract / interface #55
• Support generating sol! from ABI JSON #73

Nice-to-haves

• Move blanket SolType for SolStruct impl to sol! macro #36
• Add sol! support for enums #37
• Move define_udt! decl macro to sol! proc macro #39
• Resolve Solidity paths in sol! #82
• [Feature] Implement a trait for sol! contract events enum #163
• Support Fallback and Receive as special functions in sol-types #157, sol! macro panics when trying to process an ABI JSON file #184
• [Feature] Document impact of Solidity item visibility #254
• [Feature] Implement sol-types traits in sol! without tuples #261

[mahmudsudo]

can i take on this ?

[benluelo]

Is it planned to support resolving imports from within the sol macro? Currently sol! is largely unusable for any non-trivial contracts, since all imports have to be re-specified manually.

[DaniPopes]

Is it planned to support resolving imports from within the sol macro? Currently sol! is largely unusable for any non-trivial contracts, since all imports have to be re-specified manually.

@benluelo

No, that would be basically embedding a compiler frontend into the macro at that point which is just not worth it.

You should use JSON ABI input to pass in ABI generated from other tools, or write a simple interface inline.