question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] Importing requests from a Postman Collection v2 doesn't properly import query string parameters

See original GitHub issue
  • Insomnia Version: 5.14.7
  • Operating System: Windows 10

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:

  1. Disabled query string parameters in Postman weren’t imported at all in Insomnia
  2. The resulting URL in Insomnia contains the full URL with query string parameters. Query string parameters should have been imported in the Query tab of Insomnia instead of being put in the request URL.

Steps to reproduce

  1. Create a new GET request in the latest Postman pointing to this URL: https://httpbin.org/get
  2. Add a query string parameter in this request: first: test
  3. Add a query string parameter in this request: second: test, then disable this one
  4. Export this request as a Postman Collection v2 JSON file
  5. Import this file in the latest Insomnia

Results:

  • The URL (the one next to the HTTP method selector) in Insomnia is https://httpbin.org/get?first=test instead of https://httpbin.org/get
  • No query strings are displayed in the Query tab. There should have been:
    • first: test
    • second: test (with disabled status)

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:4
  • Comments:6 (1 by maintainers)

github_iconTop GitHub Comments

4reactions
gschiercommented, Apr 4, 2018

I think the original issue is referring to query parameters, not the :param syntax of Postman.

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.

0reactions
stale[bot]commented, Jun 13, 2018

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Importing and exporting data
To import data in bulk from a GitHub repository, do the following: In Postman, select Import > Code repository > GitHub. Confirm your...
Read more >
Importing Open Api 3.0 yaml to Postman 7.1 - Help
I Incrementally imported pieces of the document. Result: Import somewhat worked with all components of the document except path objects ...
Read more >
Using CSV and JSON Data Files in the Postman Collection ...
The Collection Runner let's you import a CSV or a JSON file and then use the values from the data file inside HTTP...
Read more >
Importing data files
Any data defined in the requests will be used when the collection runs, and your request data can reference values defined in the...
Read more >
Python's Requests Library (Guide)
Customize your requests' headers and data, using the query string and message body; Inspect data from your requests and responses; Make authenticated requests...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found