Forcing path to / results in weird defaults

[lionello]

Running resources with relative paths like ../logo.png results in assets that have a weird name like "/../logo.png" (parent of the root?).

I'd find it more predictable if the default asset names are identical to the paths used during generation. Perhaps an new option --root could be added to keep the current behavior?

go-resources/resources.go

Line 299 in 46f4269

{{range $path, $file := .Files }}"/{{ $path }}": {{ template "file" $file }},{{ end }}

[omeid]

Hello @lionello,

Sorry for late reply. In the context of web /../logo.png means parent of the current documents' directory and is used fairly often I am afraid.

A --root option is an acceptable solution, any reason you can't run resources from the a base that you no longer need relative paths?

Hope this helps.

[omeid]

Closing due to lack of response.