PATH management not hierarchical?

[shoffmeister]

Configuration management is hierarchical, https://mise.jdx.dev/configuration.html#mise-toml - but that does not seem to apply to PATH (https://mise.jdx.dev/environments/#env-path)

Imagine a configuration structure such as

• ~/baseline/mise.toml ->

[env]
_.path = ["/baseline"]

• ~/baseline/override/mise.toml ->

[env]
_.path = ["/override"]

In this case, "override" is more specific than "baseline". This works as expected for environment variables in general, but the outcome for $PATH is odd and unexpected:

/baseline:/override:/usr/local/sbin:/usr/local/bin:/usr/sbin:...

instead of

/override:/baseline:/usr/local/sbin:/usr/local/bin:/usr/sbin:...

that I'd expect.

For $PATH it is not the more specific configuration which wins. How can this be fixed? To me it seems as if management of path entries needs to be reversed in mise? (but changing that behaviour has potential for breakage)

I have tried using the above approach through variables inside the _.path, but variable-only changes themselves must be republished through _.path in order to become effective.

This is most useful (and works for the direnv tool, FWIW), when for instance a default (baseline) JDK is defined at the root of a nested git project structure, being overriden in select few places with deviations from the overall rule.