I’m starting to put some more thought into how the CLI could be better designed as a development tool and not just a utility to query the chain. I’m specifically interested in streamlining the local development workflow with the emulator.
Contract deployment and account management are two of the biggest pain points I’m seeing with both local (emulator) and testnet development. I think it’d be great if the CLI included better tooling to map contracts to accounts, especially when using the same contracts on multiple networks (emulator and testnet) or with multiple accounts on the same network.
I sketched out some ideas in this issue: Automated contract deployment · Issue #30 · onflow/flow-cli · GitHub