Include files from variable location about just

[casey]

Whoops! I neglected to extend the parser to accept shell expanded string in mod and import paths. Just merged #2059 which fixes this.

[tommyalatalo]

I would love to see this functionality implemented in a similar way to how Terraform references remote modules. Basically allow the user to enter a remote git repository URL and ref (branch, tag, commit) which would get fetched and used. This is a total game changer and would allow you to write independent justfiles in repos that reference centralized remote files as common "includes". The implications of this for use with CI systems are really quite amazing.

[peterhoeg]

How about using a git submodule (assuming you have your stuff in git of course)?

[casey]

I just merged #2055, which adds a new kind of shell-expanded string literal. They look like this x'$FOO' and can be used anywhere a string literal can be used, including module and import paths.

[laniakea64]

can be used anywhere a string literal can be used, including module and import paths.

@casey For me this syntax only works in settings, optional imports, [confirm(...)], and places where any string is valid. It does not work for me in mod statements or non-optional imports?

With this example justfile -

import x"$PWD/foo.just"

I get -

$ just --evaluate
error: Expected '*', ':', '$', '=', identifier, or '+', but found string
 ——▶ justfile:1:9
  │
1 │ import x"$PWD/foo.just"
  │         ^^^^^^^^^^^^^^^

Same error with either mod foo or mod? foo instead of import (and using just --unstable --evaluate).