Export data should include plugin's data #3596
Unanswered
codeasashu
asked this question in
Ideas
Replies: 1 comment
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
As an insomnia user, I want to be able to export all the plugin's data so that I can use third party tools on them to output something useful.
Given that the plugin ecosystem is such that any plugin can not access the other plugin's data, it makes it useless to have scattered data all around and nothing to see/do with them as a whole.
For instance, I have one plugin that keeps my responses, one that adds custom headers etc. All in all, if I am able to get those in my exports, I might be able to make use of them using any open source tools.
Describe the solution you'd like
Insomnia export has access to plugin's database. It can ask user if they would like to include plugin's data as well in the exports. Plugins can have the ability to not allow exports if they wish. Only the plugins allowing the exports will be included.
Describe alternatives you've considered
Manually going to insomnia's app data folder and opening the db file to get plugin's json seems the only way for now.
Additional context
In this PR, I am trying to add sample responses to any given request. Some useful implementations of this are:
Each of these usecases are good for their own plugins, however, they won't be able to access this data, since it is coming from another plugin (my PR is a plugin). If the exported data can include the plugin's data as well, I would've been able to do all the above, using any cli tools.
Beta Was this translation helpful? Give feedback.
All reactions