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

Allow use of flow init for existing directories #1809

Open
jribbink opened this issue Oct 28, 2024 · 0 comments
Open

Allow use of flow init for existing directories #1809

jribbink opened this issue Oct 28, 2024 · 0 comments
Labels
Feature A new user feature or a new package API

Comments

@jribbink
Copy link
Contributor

Issue To Be Solved

It would be nice to allow developers to run flow init in an existing directory. Frequently, developers will start with a Frontend project, for instance, and wish to add Cadence code to this existing boilerplate. It would be helpful to be able to run flow init in this folder to encourage interoperability with existing FE projects (the alternative now is putting whole Cadence project in separate folder, not using flow init, or using --config-only)

(Optional): Suggest A Solution

(somehow) Allow this to be possible. Would (ideally) involve checking for collisions before guiding the user throguh the init process instead of surfacing this error once they have walked through all the steps.

@jribbink jribbink added the Feature A new user feature or a new package API label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature A new user feature or a new package API
Projects
Status: No status
Development

No branches or pull requests

1 participant