Replies: 5 comments
|
Interesting, I can totally see the use case for it. Sometimes template tag expansion can also send requests, which I suppose is okay, but something to keep in mind. Provided expansion is added, perhaps you could prompt for the user to check/uncheck the option through your plugin (using a modal, for instance). I'm not sure off the top of my head how tricky it may be to add expansion, though. I do not think it would be trivial. |
Yeah, I could do that. I will be waiting for the support, thank you 🚀🚀🚀 |
|
Ah, I understand now, by |
Exactly, will be looking forward to that! |
|
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. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Template tags are not been expanded when exporting data, I need it the most in a plugin (https://insomnia.rest/plugins/insomnia-plugin-documenter) when using
context.data.export.insomniaorcontext.data.export.harand also it will be nice to have in the UI export too.Describe the solution you'd like
For the plugin system, there can be a boolean option to enable expanding template tags before exporting so developers can do something like:
And for the UI, it can simply be a checkbox when exporting.
Describe alternatives you've considered
I feel the above solution is the simplest we can ever get.
Additional context
This is what is currently happening when exporting with template tags and it doesn't look good at all.
All reactions