Environmental Variable imports from postman evaluate to "NaN"
See original GitHub issueBug
When you import environmental variables created in postman, any keys containing hyphens -
evaluate to NaN
Ex:
"api-key":"abc123"
Versioning
- Insomnia Version: 6.6.2 (6.6.2.2932)
- Operating System: macOS 10.14.5
Comments
This is probably related to #456
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:19 (3 by maintainers)
Top Results From Across the Web
Funky Behavior When Using Collection Variables (Set to NaN ...
Simply, during the request the collection variable was being set to NaN. Weird behavior, and very frustrating as the code is all correct,...
Read more >Postman Environment Variables: API Testing using ... - YouTube
What is an Enviroment in PostmanAn environment is a set of key-value pairs. The key represents the name of the variable.
Read more >Import and export data into postman and use environmental ...
Hello guysThis video is about to import and export data in postman.Also I explained how to use environmental variables to test API's on ......
Read more >Import Collections & Environments into PostMan || JSON Files
Import collections and environments into PostMan from file and from git hub url.A sample collections file and environment file has been ...
Read more >how to set environment variable in postman Code Example
postman.setGlobalVariable("refresh_token",postman.getResponseHeader("Refresh_token") );
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Totally get it. I use Twig extensively in Grav so I appreciate that Nunjucks is used for more than it appeared to me at first glance. I’ll continue on the PR. Thanks!
Bump, I created #1960 which is a duplicate (but I’ve closed it out so we can use this existing ticket).