yeah that’s the output from the test case, which i admit is confusing, is expandpath the only way to test this?

there are multiple code paths doing similar things here!

my mistake, I used {env. instead of {env:

I have adapted the test to call the config method directly

it all works and now we have test coverage, closing ticket

in the decription i see

{env.SHLVL}

but in addition i see

so that seem not to much, in any case no recent regression

added it

i have created a ticket for the log argument readability

Sure that works, i’m using that for years with Lucee 5 and 6, here a example of it.

We can do the following:

• make sure Lucee generates the same syntax in the json file as above

• create a recipe to document this

But coming back to the purpose of the ticket
do my knowledge lucee does not support {env.WHATEVER} at all, Lucee allows {enc:USERNAME} in some places, but jsut for username/passwords.

So you really need to clarifiy what you mean, i think you mix behaviours from other moving parts with what Lucee does.