flow-cli icon indicating copy to clipboard operation
flow-cli copied to clipboard

Integrate community built tools

Open devbugging opened this issue 3 years ago • 4 comments

After the initial discovery, the best way to proceed with the integration of dev-tools into CLI is to set up an environment for the dev tool as part of the install process, imagine having a command like flow flowser which would then check if required environments (node) are installed at that point it would fetch the remote build and run it locally.

This would also require good documentation of the process so others could follow the steps and get included in the CLI. This way the CLI would allow plug and play functionality. The CLI commands would also be restructured for better readability, an example is:

There could be a new section of development tools in the CLI to which community-built tools would be added as well.

Development Tools:
emulator     Starts the Flow emulator server
wallet       Starts the development wallet service

devbugging avatar May 12 '22 08:05 devbugging

I plan to add support to bootstrap an overflow project and having that as a subcommand in flow would be amazing.

bjartek avatar Sep 12 '22 06:09 bjartek

Yep. Let's discuss it. We plan to add new tools to the CLI soon. Can you explain what would the bootstrap involve?

devbugging avatar Sep 12 '22 08:09 devbugging

https://github.com/onflow/developer-grants/issues/87

bjartek avatar Sep 12 '22 09:09 bjartek

Maybe new template on flow app create ?

bluesign avatar Sep 12 '22 14:09 bluesign