-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
env files and variables are not correctly resolved #51
Comments
|
Thanks for the reply.
|
What is your folder structure in vscode
or
The second option is my own way to use the extension. |
Current folder structure is described in initial post under the second point, api specs are stored somewhere in deep structure of the project, no
|
then you need to configure ./specs/env |
Yeah, and probably this should be stored inside |
Changing Can extension also fire an exception if directory is not found? |
I have now recreated your project. I could understand the error with .env.local, but not the problem with the env folder. my project as zip #51.zip |
I have provided an update to vscode-httpyac (v2.20.0) that fixes the bug. I will continue to work on the problems with recognizing the env files using #50. |
Hello!
Here's the list of few found issues related to dotenv feature:
.env.local
,.env.production
are not properly handled, it is possible to select.local
from the list, but variables are not available within script. In the same timelocal.env
works fine.Additional question: how to log all available variables?
env
directory is not visible in the list of available environments. Structure is:Probably it will be good to have environment name to be set as a global variable, at least it gives an option to use dotenv-like packages.
Also at the moment it almost impossible to create Postman-like directory structure (or I could not figure out how):
Configuration:
The text was updated successfully, but these errors were encountered: