Can we merge mise.toml and mise.local.toml _before_ validation?

[reitzig]

I want to commit something like this to my (public) project:

[tools]
lefthook = "1.10"

It's important that all contributers (roughly) agree on the version used.

They do not, however, have to use the same shell, so I would like to put this in mise.local.toml:

[env]
LOCAL_FISH_COMPLETION_DIR = "{{config_root}}/.config/fish/completions"

[hooks]
postinstall = 'mkdir -p "$LOCAL_FISH_COMPLETION_DIR"'

[tools.lefthook]
postinstall = 'lefthook completion fish > "$LOCAL_FISH_COMPLETION_DIR/lefthook.fish"'

My expectation is that mise would merge the local config into the "main" config (knowing full well that merging dicts and arrays can be ... fun 😬). However:

 ❯ mise list
mise ERROR error parsing config file: ~/code/tools/my-project/.config/mise.local.toml
mise ERROR TOML parse error at line 7, column 1
  |
7 | [tools.uv]
  | ^^^^^^^^^^
missing version

mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information
mise ERROR error parsing config file: ~/code/tools/my-project/.config/mise.local.toml
mise ERROR TOML parse error at line 7, column 1
  |
7 | [tools.uv]
  | ^^^^^^^^^^
missing version

mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

Never mind the duplicate error ( ;) ), but: can we avoid this somehow?

[jdx]

this would not be realistic, no

[reitzig]

I found a semi-satisfying workaround by creating an "empty" task that I can call from the main config file, and implement it the local one:

mise.toml

[tools.lefthook]
version = "1.10"
postinstall = "mise run install-completion lefthook completion"

[tasks.install-completion]
run = '' # implement in mise.local.toml

mise.local.toml

[env]
LOCAL_FISH_COMPLETION_DIR = "{{config_root}}/.config/fish/completions"

[hooks]
postinstall = 'mkdir -p "$LOCAL_FISH_COMPLETION_DIR"'

[tasks.install-completion]
description = 'Install shell completions'
hide = true
run = '''
    {{arg(name="command")}} {{arg(name="completion_command", var=true)}} fish \
    > "$LOCAL_FISH_COMPLETION_DIR/{{arg(name="command")}}.fish"
'''

(see also #3757)

This works as long as all completion commands select the shell by a simple trailing argument; there's only one exception in my setup. Other devs should be able to create their own local config to install, say, zsh completions -- and if not, they get a few empty lines of output during installs.

[reitzig]

Moving the task implementation to my user config was not as graceful, unfortunately: then, run = '' wins out, lefthook completion is called (why?) and an error is thrown.

Hum 🤔

[jylenhof]

Perhaps try something like this, it's seems to works even if I find it quite ugly :

[[hooks.cd]]
shell = "zsh"
script = "mise install"
[[hooks.cd]]
shell = "bash"
script = "mise install"
[[hooks.cd]]
shell = "zsh"
script = "source <(lefthook completion zsh)"
[[hooks.cd]]
shell = "bash"
script = "source <(lefthook completion bash)"

[tools]
lefthook = "latest"

For the record, I did try to do thing like this, but that didn't work :
shell="$(mise doctor --json |jq -r '.shell.name')"

[jylenhof]

OK using templating tera I can make the script line a little bit more generic, but I don't succeed to do the same on shell line :

[[hooks.cd]]
script = "mise install"
[[hooks.cd]]
shell = "zsh"
script = "source <(lefthook completion {{ exec(command='mise doctor --json|jq -r \".shell.name\"') | basename }})"
[[hooks.cd]]
shell = "bash"
script = "source <(lefthook completion {{ exec(command='mise doctor --json|jq -r \".shell.name\"') | basename }})"

[tools]
lefthook = "latest"

[reitzig]

I'll have to try, but it would surprise me if that worked. Unless mise somehow gets the hook code into a fish function (theoretically feasible through activation, I guess?), it'll shell out for the call and sourcing there shouldn't change anything in the shell that called mise. Or is my understanding completely off somehow?

Also, is there a particular reason to use hooks.cd over hooks.enter? 🤔 I'd rather use the latter because it's more targetted, and would have assumed that basic behaviour regarding things like source would be identical.

Plus: #4378; don't recall if I tried to run hooks in fish; tasks definitely didn't work.