"envDirName" does not work ("dotenvDirname" does)

[jg-cantaa]

The envDirName Setting does not work, although it is the option documented to work everywhere.
VSCode doesn't even recognize the option as valid.

[AnWeber]

I think the cause is the typo in the path of httpyac.envDirName. I search for folder env by default. The search starts from folder of the http file and searches for the following files/ folder upwards (package.json, .httpyac.js, httpyac.config.json, env). However, since envDirName is now overwritten with .spec/env, it cannot find root and read the files. Commenting out envDirName fixes the error and it will find the files again.

[jg-cantaa]

So, after doing some experimenting I am still quite confused. Although the issue title does no longer apply, I am still having difficulties getting this to work. So I will try to explain how my current understanding is:

Assuming I have the folder structure

.vscode/
    settings.json
specs/
    api/
        request.http
    env/
        .env.test

• It searches for the envDirName Folder first in the following places and order:
  • specs/api/<envDirName>
  • specs/<envDirName>
  • <envDirName>
• If it finds a matching folder, It does not try to continue searching for other matching folders.
• specifying envDirName with a absolute path will work
• if the path is not absolute, it seems to have trouble resolving paths with more than one segment (e.g. Specifying envDirName to be test/env only finds environments in the first test folder it finds.)

In all honesty, this seems overly complicated to me, although I might not have the full picture and there might be valid reasons for this. The Documentation in the readme states "relative or absolute path to folder with dotenv files", which from my experimentation does not hold.

Could this be adjusted to reflect the description given in the readme?

[AnWeber]

The issue for the root folder determination is #50. Use case is that different environment variables can be set for different requests in the same project. Many Tools like tsc, eslint or Prettier also support such a config search.
And if you use it in the standard way, your example would just work without changing envDirName.

if the path is not absolute, it seems to have trouble resolving paths with more than one segment (e.g. Specifying envDirName to be test/env only finds environments in the first test folder it finds.)

Nested envDirName I have not considered correctly, and overlooked during implementation But I would recommend to just use the default one. I left the setting mainly for absolute file paths to allow cross-project settings or as hidden folder support in Linux.

[AnWeber]

fix is released with v4.8.2. Thanks:-)