Ability to dump script for validation/linting

[bluefing]

Hi @casey

Is there a way to capture recipe bodies.

In general I try to write scripts (bash or otherwise) and invoke them from recipes so that I can test behaviour using e.g. bats with mocking for bash, pytest for python etc. This also allows me to lint the recipe bodies using pre-commit hooks.

However, there are cases where I don't want to do that e.g. a remote justfile where I want everything in a single file to simplify fetch.

--dry-run is close but you need to know which args the recipe expects and it interpolates.
--show gives the whole recipe
--dump is raw

I had a look at the docs and the cli args but I can't see a way to do this.
I know that just writes shebang and [script] recipe bodies to a temp file in a directory that I can control via e.g.

just --tempdir=~/dev recipe

and if the script is blocking I can indeed see the script written to the directory, however just is too well behaved and cleans up after itself, and even then the shebang is not included.

Hopefully I am not missing something obvious
Cheers

[casey]

Hello! Do you want the recipe bodies before or after interpolation?

[ShreeChaturvedi]

There is no flag that prints only a recipe's script body. That request is still open in #737 and #1456.

Before interpolation, with no args:

just --show RECIPE
just --json

--show prints the formatted recipe, including the name line, docs, and attributes. --json is --dump --dump-format json. Each recipe's body is parsed fragments, not the source text. A string is literal text. An array is a {{ }} interpolation.

After interpolation:

just --dry-run --no-dependencies --no-highlight RECIPE [args]

Evaluated lines go to stderr. Shebang recipes keep the #! line. [script] recipes do not, because just invokes the interpreter on a tempfile and never writes a shebang. Those tempfiles are deleted after the run. --dry-run never writes them.

Linting wants the after-interpolation form so tools do not see {{foo}}. You still have to pass required args.