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

Make a skeleton in the current or existing folder (phalcon project) #1126

Open
4iloveg opened this issue Oct 17, 2017 · 1 comment
Open

Make a skeleton in the current or existing folder (phalcon project) #1126

4iloveg opened this issue Oct 17, 2017 · 1 comment
Assignees
Milestone

Comments

@4iloveg
Copy link

4iloveg commented Oct 17, 2017

At this point, the project skeleton is deployed to the folder with the specified name. But if you try to install it into the current or existing folder (even if they are empty), an error message will appear.

сurrent implementation

phalcon project .

Error: Directory D:\OpenServer\domains\phalcon.loc\.\ already exists.

it's desirable

phalcon project . --force

Success: Project '.' was successfully 

An error when deploying to an existing folder may be caused by the intention not to damage the files that are located.
But I would like to be able to implement the deployment forcibly.

@Jeckerson Jeckerson modified the milestones: 3.4.x, 4.0.0 Mar 15, 2019
@Jeckerson Jeckerson modified the milestones: 4.0.0, 4.1.0 Nov 10, 2019
@Jeckerson Jeckerson modified the milestones: 4.0.x, 5.0.x Mar 12, 2021
@Ultimater Ultimater self-assigned this Jul 8, 2021
@Ultimater
Copy link
Sponsor Member

I believe at the very least the error message should mention the existence of the --force flag.
I can see the use case of people creating a blank directory then cd'ing into it very common, and no reason to request the --force flag provided it is indeed a blank directory. If it's not a blank directory, I think showing an error message, which mentions the --force flag is in the best interest of the user so they have a chance to review and verify they know what they are doing. Then if they are sure, they can run the command again with the --force flag.

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

No branches or pull requests

5 participants