Open MelGrubb opened 11 months ago
I've made the journey from Postman to SmartBear to Thunder to Insomnia, and finally to Bruno in search of a simple, non-subscription-based tool that would let me store my request collections in source control. This is important to my team so that one developer making breaking changes to an API doesn't break everyone else in the meantime. The collections live in the branch they apply to, as it should be. Congratulations, this is a great project.
About the only thing I'd like to see is Insomnia-like, json-based environment definitions. It was the only thing about Insomnia that impressed me, certainly not the request chaining mechanism... that's terrible. Anyway, the moment I saw the json-based environments, I realized they were the thing I'd been missing. I didn't even know I wanted them until I saw them, and now I can't imagine any other way to store environment variables for collections.
As I said in the issue, we use pseudo-hierarchical environment variables, primarily because none of the tools (other than Insomnia) would allow us to create actual hierarchical environment variables. So, we end up with variables like "Auth0-Api-MyProject-ClientId", or "Auth0-User-QA-Admin", or "Auth0-User-QA-Client01". This means that all of our variables can have rather long names, and they just don't fit in the space afforded by the dialog right now. I can work around this by just editing the file directly, of course, but it would be nice to be able to see them directly in the UI.
I don't like this narrow and in case of many variables to high environments dialog too. I think the best approach would be to change it to tab. To have it the same as collection settings, runner, collection variables tab, ...
Currently if there are too many variables defined then I have to scroll dialog down to see some actions/buttons which are at the bottom and then scroll up to see actions/buttons which are at the top. Also variable name column is too narrow, so I have to select text and "move" it to see what is at the end in variable name.
Came here to raise this issue, but in doing so, I realised that actually having a modal for environments isn't practical at all. Environments would be much better if they popped up as a tab, so I could flick to-and-fro easily.
The primary driver for this is that because there is no environment hierarchy, my names have to have long prefixes, so, within a dialog, they all look the same.
A tab is a much more convenient way of doing this.
Our project uses pseudo-hierarchical names for the parameters to keep them organized. The Environments dialog is too small to read the longer names. The dialog should be resizable, as well as the columns in the table.