-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Bug] Importing requests from a Postman Collection v2 doesn't properly import query string parameters #778
Comments
👋 Thanks for opening your first issue! If you're reporting a 🐞 bug, please make sure To help make this a smooth process, please be sure you have first read the |
Okay, I just saw the Import from Url button at the very bottom of the screen in the Query tab that would have done the job... But still, query string parameters should have been properly imported. |
AFAIK insomnia doesn't support URL parameters like postman :/ |
I think the original issue is referring to query parameters, not the The problem is that right now, query params defined in Postman in key-value form are imported into Insomnia as a single string, appended to the URL. Instead of this, it should be imported into Insomnia's key-value form within the Query tab. |
@gschier is absolutely right 😄 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Details
Using the latest standalone version of Postman on Windows: I exported a collection of requests to a Postman Collection v2 JSON file.
I then imported this file in the lastest Insomnia on Windows (by dragging / dropping the file directly in the window): the import were successful, however query strings parameters weren't properly imported. Specifically:
Steps to reproduce
https://httpbin.org/get
first
:test
second
:test
, then disable this oneResults:
https://httpbin.org/get?first=test
instead ofhttps://httpbin.org/get
first
:test
second
:test
(with disabled status)The text was updated successfully, but these errors were encountered: