Current Behavior
In this screenshot, first installation to non-empty directory shows expected behavior, with fcli asking the user to confirm cleaning the target directory.
However, once a specific tool version has been registered with fcli (through the first install command in this example), new installation to a different non-empty directory fails with an exception, without giving the user the option to clean the target directory. Same failure is seen if user explicitly passes -y in the install command to auto-confirm any prompts.
Expected Behavior
The fcli tool * install commands should ask for confirmation to clean a non-empty target directory independent of whether that tool version was previously registered (in same or different location).
Steps To Reproduce
See screenshot above
Environment
Anything else?
Likely closely related to #976
Current Behavior
In this screenshot, first installation to non-empty directory shows expected behavior, with fcli asking the user to confirm cleaning the target directory.
However, once a specific tool version has been registered with fcli (through the first
installcommand in this example), new installation to a different non-empty directory fails with an exception, without giving the user the option to clean the target directory. Same failure is seen if user explicitly passes-yin theinstallcommand to auto-confirm any prompts.Expected Behavior
The
fcli tool * installcommands should ask for confirmation to clean a non-empty target directory independent of whether that tool version was previously registered (in same or different location).Steps To Reproduce
See screenshot above
Environment
Anything else?
Likely closely related to #976