本文介绍了如何从Postman导入并确保所有环境变量都可以解析?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有大量的Postman定义,每个请求都包含一个或多个Postman样式的变量,例如{{HOST}}.对于我的每个Postman环境,这些值显然都不同.我已成功将所有环境导入到Paw中,然后导入了我的一个集合,但是似乎没有一个变量被转换为Paw样式的变量,因为我必须转到每个变量并删除类似的变量{{HOST}}赞成从头开始重新键入{HOST},以便它将解析为适当的环境变量占位符.我试图破解导入的文件以及导入程序扩展名,以使其无法提交,但无济于事.真的没有办法让这些变量作为占位符导入吗?

I have a pretty large suite of Postman definitions, and every request contains one or more Postman-style variables, e.g. {{HOST}}. The values for those are obviously different for each of my Postman environments. I have successfully imported all of my environments into Paw, and then I imported one of my collections, but none of the variables were converted into Paw-style variables, it seems, because I am having to go to each one and delete the likes of {{HOST}} in favor of re-typing from scratch {HOST} so that it will resolve to the proper environment variable placeholder. I tried hacking the imported file as well as the importer extension to beat it into submission but to no avail. Is there really no way to get these variables to import as placeholders?

推荐答案

更新:Paw在如何从Postman迁移到Paw

答案可能为时已晚,但是我们最近对Postman Importer进行了改进,因此所有变量标签(如{{variable}})现在都可以解析为环境变量: https://luckymarmot.com/paw/extensions/PostmanImporter

Probably late for an answer, but we've recently improved the Postman Importer so all variable tags (like {{variable}}) are now resolved into environment variables: https://luckymarmot.com/paw/extensions/PostmanImporter

这篇关于如何从Postman导入并确保所有环境变量都可以解析?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-28 22:27