-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Renaming Funtion names #50
Comments
I think for now, restore would be logical but we can change this later. restores looks meaningful with backup . <RESTORE_OPERATIONS> ::= Config "Only restores dots from default"
| Clone "Restores dots from a clone repository"
| BackUp "Restores dots from previous backup"
| Link "Links a clone directory. Useful if you want to change your CloneDir" wont make much sense with deploy I guess |
I'm not bothered with |
How about something like |
@saharshbhansali but apply is sounding more specific to something than the config. Look, this is the list of available functions. IMO, Will wait for other's opinion regarding this things. Or will make a poll in DC. |
@kRHYME7 Yeah. That makes sense. How about just That's the most direct way. And the description can be updated to And then add flags/subcommands for the other features, like backup and the like. |
Actually I think deploy is good. As you're taking the dotfiles from a directory and then "deploying" to dotconfig. The meaning of deploy itself looks to suit this pretty good I guess/ |
Restore does feel like restoring original dotfiles lol. I guess you should look at the meaning of the word itself and decide. |
Hi to anyone that might be using the CLI, I needed your suggestions on naming the funtions.
change restore => deploy
I will start with
Hyde restore [args]
. Would it be fine if we use the termdeploy
? The reason for calling it restore is to restore Configs to the local $HOME. This term is meaningful if you fork the repo or owner of the repo. New users don't find the meaning to this and thinks that there configs will be restored back LOL.Is
deploy
Fine?The text was updated successfully, but these errors were encountered: