Please search for related topics, and then read through the guidelines before creating a new issue.
Describe the bug
When I import an API spec (on the APIs tab), it’ll import the spec and allow me to generate a collection based on that spec which is great. However, I have to go to the collection in order to generate the documentation which leads me to believe that process ignores the spec and simply generates the documentation from the test itself which wouldn’t have a response model. This is seen when you view the documentation as the response objects are nowhere to be found. Is this intended or is there something else that I’m missing.
Steps to reproduce the behavior:
- Go to APIs tab
- Import an API that has endpoints with both request and response models defined.
- Have the API generate a collection
- In the collection, publish documentation
- Review documentation and see that there are no response models.
The generated documentation should have both request and response models.
App information (please complete the following information):
- Native App
- Postman Version 7.5
- OS: Windows 10 1803
We’re really looking for something that could provide us with and effect similar to a central swagger repository.