Repository navigation
Dont ask for OVERWRITE if the filepath does not exist #428
Description
Activity
- changed the title
[-]Dont ask for OVERWRITE if the file does not exist[/-][+]Dont ask for OVERWRITE if the filepath does not exist[/+]on Jul 26, 2024 Hey @slm0n87 thank you once again for your feedback!
In commands that make changes (
create,update,delete, etc), we have the common practice of asking the user for confirmation. This is also common behaviour in other CLI's and in programs in general.
However, if you don't want to be prompted for confirmation you can always provide the--assume-yesflag, which will bypass the prompts and remove the user interaction from the command.Kind regards,
DiogoThx @DiogoFerrao, the
--assume-yeshelped me in that case.I agree that its common behaviour and best practices for CLI's before overwriting existing files.
But I am not aware of any CLI where I explicitly specify a file as argument and I get prompted to confirm that I really want to save it there.Regards,
SimonThat's a good point @slm0n87, I think this is also one of the few commands that interact with files in the user's system and not STACKIT resources that come with costs.
We could consider having a check and only prompt the user for confirmation when actually overwriting a file. We will add this topic to the our backlog and keep you updated on its progress!
Reacted by Simon Stier
Doing:
The cli gives a warning to overwrite the config file if it exists and have a default: No.
This is very nice, but absolut unnecessary if the file des not exist.
Expected behaviour:
Just write the file and avoid unnecessary user interaction.