I've written a small change PR which will add the above to cmd/build.go which appears to do what I want. I'll submit that momentarily.
I can't oversee how interoperability of these filepaths might work with longer subdirs for queries and templates.
Not for the other places in the code where regular slashes are used.
Any slashes (regular /) do work as expected in the view output and create subdirs in the output site.
Love this project! Using the example from the README, I've made a
views.yaml
file containing:This works as expected on Linux (Ubuntu 20.04 [self compiled, following instructions]), but using the precompiled Windows binary:
The Windows binary works when the
views.yaml
file is as follows, but then it wouldn't work on the Linux runner.I haven't written Go before, but perhaps
filepath.Walk
in https://github.com/glaciers-in-archives/snowman/blob/7e070914e2ee8cde3d8c70f861220b2763045016/cmd/build.go#L46-L56 uses, likefilepath.WalkDir
operating-system specific path separators. Thestrings.Replace
call then might be able to use something like"queries" + os.PathSeparator
?I've written a small change PR which will add the above to
cmd/build.go
which appears to do what I want. I'll submit that momentarily.I can't oversee how interoperability of these filepaths might work with longer subdirs for queries and templates. Not for the other places in the code where regular slashes are used. Any slashes (regular
/
) do work as expected in the view output and create subdirs in the output site.