The main feature of this release is the ability to import collections from Postman.
Simply export your collection from the Postman UI, then run:
posting import --type postman path/to/collection.jsonHere's Posting in action, browsing collections and sending off requests - all of which have been imported from Postman.
posting-postman-import-example__80pct_smaller.mp4
Changelog
Posting's full changelog is always available at https://posting.sh/CHANGELOG/.
Added
- Collections can now be imported from Postman (#106)
posting.envfiles in the current directory will automatically be loaded if no--envoptions are provided (#249)- Generate JSON body with default values after importing OpenAPI specs (#247)
- Use tags to separate sub-collections in OpenAPI specs (#247)
- curl import now handles various different data options (#252)
- Added
-cshorthand alias for--collectionoption (#250) - Added
posting sponsorscommand, which lists people who have supported Posting via GitHub Sponsors (specific sponsor tiers only). (#253)
Changed
- A double-click rather than a single-click is now required to enter edit mode inside data tables (e.g. headers, query params, etc.) (#256)
- In the body editor, the
Form datamenu item now shows(x-www-form-urlencoded)after the label, to suggest the type of data being sent. (#259)
Fixed
- Exported curl command uses
-dfor form data now, rather than-F. The result is exported commands with form data will now useapplication/x-www-form-urlencodedinstead ofmultipart/form-data(matching Posting's behaviour). (#252) - Fix attempting to add a protocol before applying variables in the URL bar (#248)
- Fix script path with custom function (#254)
- Fixed Posting's default
User-Agentheader not being used (#259)
New Contributors
- @ll931217 made their first contribution in #106
- @jonahisadev made their first contribution in #254
Sponsors
- A huge thank you to @elithper for sponsoring development of Posting via GitHub Sponsors!
Full Changelog: 2.6.0...2.7.0