@UJSBQNUG6 This is implicitly already there in the form of:

(fs/file .. .. ..)

or (fs/path .. .. ..), If you want to have a string, call str on it

hmm, okay, that works

don’t you think it would be convenient to have such thing?

I don't see the need for it since it's already there

okay, I missed the fs/path one

thank you!

cli/format-opts is great, but I cannot see how could I display the command table in a nice way

@UJSBQNUG6 For the command table it's not there (yet), I've done it manually so far

E.g. in neil: https://github.com/babashka/neil/blob/65a078a24462ab06fc7bc3bd5e240f4adfaa7f8a/src/babashka/neil.clj#L629 I print a global overview and then use format-opts to print the details for each subcommand

there is a bit of duplication here and there

but it works, thanks!

I suspect there won't be a single way that fits every subcommand need, but maybe it's worth a shot one day

that is fine, I thought there might be something but I am blind as I proved earlier 😄

no worries, keep asking away ;)

yes, use require + :reload

Right now you must specify relative paths for entries that will be mirrored in the resulting zip. Specifically right now I'm trying to remove this babashka shell call to zip.

(shell {:dir "root-dir"}
  "zip" "myzip.zip"
  "file1.txt"
  "file2.txt"
  "file3.txt")

(fs/zip "myzip.zip" ["root-dir/file1.txt"
                     "root-dir/file2.txt"
                     "root-dir/file3.txt"]
  {:relativize-entry-paths "root-dir"})

(fs/zip "myzip.zip" ["root-dir/file1.txt"
                     "root-dir/file2.txt"
                     "root-dir/file3.txt"]
  {:entry-path (fn [p] (fs/relativize "root-dir" p))})

(fs/zip "myzip.zip" {"file1.txt" "path/for/file1.txt"
                     "file2.txt" "another/path/file2.txt"})

I sort of like the last option the best, but interested in any input. Also open to the idea that this is getting too fancy with zipping functionality for a general file library, and it should be somewhere else.

This issue may be related: https://github.com/babashka/fs/issues/67

> Another more general option might be to allow a function to be passed to transform an entry to the path that will appear in the zip, I think this will be the most flexible option

but do I understand correctly that you just want to get rid of the parent directory, like in that issue?

I want to use a different directory as the parent directory, which I think is different

I have stuff/f1.txt and i want it as f1.txt in the zip

yes, this is what I mean with "elide parent directory" in the issue

you want to elide stuff in the zip

but a :path-fn or so would be good, then indeed you can call relativize

One thing I realized I missed is the case where a directory is specified as an entry. Presumably the path-fn in that case would return the entry path of the directory. And then the contents of that dir are all given a path relative to that in the zip

Maybe best to try out in an experimental PR or so

will do, thanks for the input!

@U064UGEUQ I went ahead and added both :root and :path-fn - it's released, see #C06MAR553

I will release a new bb tomorrow morning with this included as well

Awesome, thanks!