Programmatically export data

Hi!

Scenario

• API hosted on Github, team uses Insomnia to work on it
• API documentation served on my webhost, using Insomnia-Documenter https://www.npmjs.com/package/insomnia-documenter, with latest fixes by me it runs smoothly in every cases

Problem

Insomnia Documenter uses the export json file to create a nice looking documentation: https://api.projectalice.io/ . This json file can be obtained by exporting the Insomnia data as in: application => preferences => data => export, but not programatically using inso cli. This leads to me having to pull the latest changes made by the team, daily, export the data and upload it to my webhost.

Possible solutions

1. CLI command to export the data, in the inso npm package. This would allow Github actions to install the CLI and export the data in the desired format.

• PROS: integrated
• CONS: one more step

1. The Insomnia “push” function does, if setting enabled to, export the data and include them in the commit/push

• PROS: totally transparent, no extra steps, awesome
• CONS: not intuitive as includes extra data to a commit without the user to be really aware of it. Would also need branch settings and others.

1. Have insomnia documenter use not the exported data, but the raw data available on Github

• PROS: Nothing for you guys to do, works out of the box
• CONS: Unlikely to happen as the documenter dev is very busy

1. Feel free to add in comments

Benefits

Having such a function would allow a totally automated workflow when pushing new data on the API repo, allowing everyone to generate nice documentation without any hassle. I must say, it competes easily with Postman

[smacktoid]

That is interesting. Hadn’t realised the designer could be used in that way.

Unfortunately issue 2639 means I can’t use git sync with our corporate git repository, but if that ever gets resolved it looks promising.

[nijikokun]

I think this is definitely something suited for Inso, as we have export functions for Designer but not Core.