Closed NiewView closed 1 year ago
I overlooked that the search for the httpyac config files always returns a folder and that's why the fallthrough to the search for package.json and env files doesn't work. I have corrected it.
it is fixed with v6.4.6.
.env files are still not being picked up correctly in v6.4.6 either (had the same issue with v6.4.5).
Root directory of my project has a /env folder which contains a local.env file (with a few variables). However, I am unable to switch to this config via the VSCode Environment selector menu.
However, v6.4.4 seems to be working fine.
@rishigharpuray-ag The env directory name is configurable. But unfortunately I have removed the fallback to 'env'. Workaround is currently to configure it manually. I will make an update tomorrow where I will add this back. I am also currently writing tests where I can mock the filesystem extensively and test the constellations for me. i thought they were already there.
Hi,
it seems like since the latest release 6.4.5 the env directory is ignored. It does not mark the root of a project anymore (as described here https://httpyac.github.io/config/#project-root), nor do the environment files get included in the environment selection.
I have a repository, with an env dir like this without a package.json or .httpyac.json:
The enviroments Test1 and Test2 are not found:![image](https://github.com/AnWeber/vscode-httpyac/assets/20443472/ecff46a8-9600-4e69-80dd-dfc1223e1d3e)
Even if I add a .httpyac.json like this there are no environments:
only when I directly add them into the httpyac config files a environment is shown:
I guess it is a side-effect of the fix for #194