-
Notifications
You must be signed in to change notification settings - Fork 4
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
File path slashes not working in Windows #16
Comments
I can confirm, this has impacted me as well on Windows. |
Seems that this repo is not maintained anymore. I have created a fork of this plugin and fixed the issue in the plugin. Unfortunately, it seems that Insomnia has a general issue with escaping. So I changed the type of the .env file parameter to a string, to be able to enter an adapted path with an own escape sequence. For Windows instead of backslashses forward slashes must be used. And these forward slashes must be escaped with a backslash. Forked plugin: https://www.npmjs.com/package/insomnia-plugin-fpf-dotenv (installation via npm package insomnia-plugin-fpf-dotenv). |
@pfefferf Thank you for raising this and for your patience. I haven't been able to respond for a while. I will close this issue for now, but happy to look at it again if the problem persists. |
Hi Version: Insomnia 10.1.1 Plugin ver.: 1.2.0 we can confirm that this still happens. Just installed this plugin, so please bear with us. What additional info can we provide? Edit tag dialog, for a variable in base environment: Variable used in Auth tab of a folder: Edit variable dialog. Actual path is |
Describe the bug
When in Windows, the resulting file path in the Edit Variable preview is missing all folder slashes in Windows.
Example: "C:\Users\someuser\secret_file.env" becomes "C:Userssomeusersecret_file.env"
This causes an error: "ENOENT: no such file or directory, open 'C:Userssomeusersecret_file.env'"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect the Edit Variable to pull in the value of the variable with no error.
Screenshots
Desktop (please complete the following information):
Additional context
I notice that the error is different if you use a dotenv in a Sub Environment. It doesn't bother to output the file path at all.
Also, I've tried the same project and same file in Linux, and this plugin works fine.
The text was updated successfully, but these errors were encountered: