Skip to content
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

Closed
srinjoyc opened this issue Feb 10, 2022 · 6 comments
Closed

Add a flow.json file on export of a playground project #225

srinjoyc opened this issue Feb 10, 2022 · 6 comments
Assignees
Labels

Comments

@srinjoyc
Copy link

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.

@srinjoyc
Copy link
Author

We could try exporting a bash/shell script to run the initial account setup @MaxStalker

@MaxStalker
Copy link
Contributor

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.

@kerrywei
Copy link

kerrywei commented May 9, 2022

Per confirmed with Max -- this task can be handed over

@srinjoyc
Copy link
Author

Add a readme with a project export for instructions

@bthaile
Copy link
Contributor

bthaile commented Apr 27, 2023

not going to add flow.json
cli can generate one for an exported playground project. closing

@bthaile bthaile closed this as completed Apr 27, 2023
@github-project-automation github-project-automation bot moved this from 🔖 Ready for Pickup to ✅ Done in 🌊 Flow 4D Apr 27, 2023
@DylanTinianov DylanTinianov reopened this Apr 27, 2023
@DylanTinianov DylanTinianov moved this from ✅ Done to 🔖 Ready for Pickup in 🌊 Flow 4D Apr 27, 2023
@DylanTinianov DylanTinianov moved this from 🔖 Ready for Pickup to 🏗 In progress in 🌊 Flow 4D Jun 5, 2023
@DylanTinianov DylanTinianov moved this from 🏗 In progress to 👀 In review in 🌊 Flow 4D Jun 20, 2023
@DylanTinianov DylanTinianov moved this from 👀 In review to 🏗 In progress in 🌊 Flow 4D Jun 20, 2023
@bartolomej
Copy link

bartolomej commented Aug 19, 2023

I wonder if the export feature could be adapted so that instead of downloading the exported project in the browser, the flow setup command could be used to scaffold a project given a flow playground URL.

Obviously, this would some changes on the Flow CLI side (e.g. adding a separate flow setup --playground <URL> flag or detecting the type of scaffold and then implementing the exporting logic).

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 flow.json file, since I believe Flow CLI could do that easily during the scaffolding process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

9 participants