Renaming Funtion names

[kRHYME7]

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 term deploy? 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?

[rubiin]

I think for now, restore would be logical but we can change this later. restores looks meaningful with backup . Also the restore options,

<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

[kRHYME7]

I'm not bothered with restore though. However, I will leave this topic open for a while. Needed some suggestions on other functions too. GN

[saharshbhansali]

How about something like apply? It clearly indicates that you want to apply configs from whichever source you specify.

[kRHYME7]

@saharshbhansali but apply is sounding more specific to something than the config.

Look, this is the list of available functions. IMO, apply is not too specific for restoring the dotfiles.

Will wait for other's opinion regarding this things. Or will make a poll in DC.

[saharshbhansali]

@kRHYME7 Yeah. That makes sense.

How about just configure, then?

That's the most direct way.

And the description can be updated to apply the configuration from the files in [FILEPATH] or something like that.

And then add flags/subcommands for the other features, like backup and the like.