search

Andriamanitra / coctus

Command line tool for playing Clash of Code locally
MIT License
4 stars 2 forks source link

Add `clash save` command #42

Closed daxida closed 2 months ago

daxida commented 7 months ago

Probably just the bases for fixing #20 in the future. I don't think I'll be able to manage the browsing or other features discussed there.

daxida commented 7 months ago

I have no experience with sqlite3 so I can't comment on that. If we end up going that direction maybe you can give me some pointers.

For the build command, I don't see how to include it other than either manually adding it to the save command (some flag), or fetching it from a configuration file that would have been set up previously for clash run.

The way I see using this myself would be mainly to store valid solutions (so personally I find no need for a build command, I will probably very rarely run those again). That only requires moving them and eventually adding a renaming option to the command.

Andriamanitra commented 7 months ago

The way I see using this myself would be mainly to store valid solutions (so personally I find no need for a build command, I will probably very rarely run those again). That only requires moving them and eventually adding a renaming option to the command.

IMO just saving a solution file is a task for a shell script rather than clash. A shell script that uses mv is easier to change (no compilation step) and more flexible (you can easily make the filename and location be whatever). Maybe this use case would be better served by a command that prints the handle of the current clash so you could use it like this?

mv $FILENAME ~/my/clash/solution/directory/$(date +"%Y-%m-%d-%H%M")_$(clash showhandle)_$FILENAME
daxida commented 2 months ago

I do not think this PR is going anywhere, should we close it?