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.
Issue To Be Solved
It would be nice to allow developers to run
flow initin 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 runflow initin this folder to encourage interoperability with existing FE projects (the alternative now is putting whole Cadence project in separate folder, not usingflow 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.