Import from Postman Collections
JetBrainsJetBrains · v—
Starting from 2023.3, all features of the Import from Postman Collections plugin are incorporated within the HTTP Client plugin . Converts Postman Collection files to .http format of HTTP Client plugin
Rating distribution
Reviews 8
when i convert xxx.postman_collection.json to xxx.http file. it while lost "client:secret@" in the "http://client:secret@localhost:9000/oauth/token",but it works in import from "cURL command..." (not lost "client:secret@" )
It is not intuitive. Documentation lacks information that the file has to be named abc.postman_collection.json Postman exports file without "postman_collection" part and then the plugin does not recognize such file
Seems interesting, but i encountered some strange behaviors that negate my test. First of all, as reported in IDEA-333860, the postman files must not be renamed otherwise they dont even appear in the import dialog. Then, when the postman collection already contains tests, the import fails silently. I had to remove manually those tests while I thought the import could just comment them if he...
It works excellently in importing all the requests but lacks auto-adding collection-level authentication headers to all the requests.
Cannot get it to work. Nothing happens when I import.
Plugin does not work (version 1.0.4). It fails silently and does not create any IntelliJ HTTP files.
Updates are required to be compatible with 2023.3.4
Since it updated to v1.0.0 from rc1, I'm unable to update. Even if I do update it crashes. I already submitted crash report via IDE though.
Similar in “Tools Integration”
Docker
JetBrains
Lombok
JetBrains
Space
JetBrains
Terminal
JetBrains
Gherkin
JetBrains
JRebel and XRebel
Perforce