-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add a flow.json
file on export of a playground project
#225
Comments
We could try exporting a bash/shell script to run the initial account setup @MaxStalker |
I started the work on implementation via shell scripts, but atm it's stalled in favor of #251 - which affects more users and should be fixed right away. |
Per confirmed with Max -- this task can be handed over |
Add a readme with a project export for instructions |
not going to add flow.json |
I wonder if the export feature could be adapted so that instead of downloading the exported project in the browser, the Obviously, this would some changes on the Flow CLI side (e.g. adding a separate But I imagine having a consolidated way of setting up / scaffolding new projects would contribute towards a better DX. Plus this could also solve the issue of generating |
Is your feature request related to a problem? Please describe.
When exporting playground projects, we should supply a flow.json with arbitrary keys on accounts that can be immediately used with the emulator locally. This would make it much easier to go from experimentation on the limited playground features to a local environment to continue building. The goal would be to have minimal friction and configuration between playground and emulator + CLI and have the contracts, scripts, and transactions work out of the box.
Describe the solution you'd like
Each account should have a set of keys.
We should replace the cadence imports with appropriate aliases/relative paths so the scripts can be run.
Contracts should be easy to deploy and scripts and transactions should work without further modification.
The text was updated successfully, but these errors were encountered: