Hi,
I have turned on the types. So that i can give my Path Variables and Query params Additional properties.
But when i make a export i don’t see the information inside the json. Why is that not included. Is this a bug or is this not implemented yet?
Hi @dannyblok Shashank here the PM on the initiative. May I know what’s the reason to export the collection? If it is to share with your teammates, creating a team on Postman and adding your teammates to the team and workspace is the way forward. This will lead to an effective collaboration rather than an error prone export and import.
Hi Postmanaut, the type feature is wonderful!
My use case in need for importing/exporting is two-fold:
We as an API provider need to export collections to provide them to our customers for onboarding reasons. I am aware that we can collaborate with partners in a shared workspace. As we are in the buying process of the according plan, and I do not have access yet, I am worried that the type information might get lost when copying our template to an externally shared workspace. Maybe I am needlessly worried? Would be great to know.
The other use case is that I regularly export and re-import collections to make bulk-changes in my IDE. For example if a repeating sentence in a description of a query parameter needs to be exchanged accross the whole collection. Or, as I like to do (maybe the only person), to replace placeholders I enter in my template to individualize a collection to a specific customer with a script. The latter has been of great help at my old company. Now it looks like I need to choose between individualization and new features.
All in all, I am surprised to find that a tool as excellent as Postman is not exporting all data I curated in that tool…