[Feature Request] Edit Variable...allow me to actually edit the value of the variable, not just change variables

[sturose]

Is your feature request related to a problem? Please describe.
I want a quick way to edit the value of a variable. I can see the variable being used, I can click on it. A box comes up named 'Edit Variable'...but all I can do is switch the variable, but not edit the value.
I see a Live Preview box that I can click on, but it isn't editable.

Describe the solution you'd like
I'd like to be able to click on the Live Preview box and actually edit the value associated with currently selected Environment Variable

[sturose]

Is there any thoughts on the feasibility of this from a dev's perspective? Right now, in order to edit a variable's value, I have to click 3 times, then find the element by eye inside of a json object to update it, which is quite cumbersome.

[mebius01]

I have the same difficulties. I would be glad if this functionality was present

[develohpanda]

Is there any thoughts on the feasibility of this from a dev's perspective?

This is feasible off the top of my head, but it may be fairly involved so some exploration would be worthwhile. The environment variable source (root environment, sub environment, folder) is provided, as well as the JSON path of the variable (eg. a.nested.variable). Another option may be to open the environment editor and highlight the variable, rather than adding edit functionality to this modal.

[stale]

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.

[ntextreme3]

After searching I kept winding up at "request chaining" issues and almost opened a new request and finally found this 😃

This is what I'm looking to do as well -- just be able to edit the environment variables in a faster way.

Another option may be to open the environment editor and highlight the variable, rather than adding edit functionality to this modal.

I think even if this functionality was completely separate from the modal that would be nice and solve this issue. Something like: "ctrl+click" on variable name takes you right there on the Manage Environments modal to edit it, bypassing the Edit Variable modal completely 👍

[kreosus]

Hi @sturose
Good day and I hope that all is well. Have you tried our newest release located here: https://github.com/Kong/insomnia/releases/

[sturose]

@kreosus This still is not working as I was hoping for in the latest release.

Getting the Edit Variable dialog gives me to something like

But I don't want to switch away from using the variable, I want to change the value of variable. In order to accomplish this I need to click on the collection -> Manage Environments -> then click to the appropriate environment/base environment.

But it would be so much nicer if I could edit the value that the variable it set to within that Edit Variable dialog.

If I could edit the Live Preview and it persist to the appropriate place, that would be ideal (although renaming it from Live Preview would probably be in order).

[ntextreme3]

+1, was there some new functionality that was added to address this? I didn't see anything that looked related in the last couple bunch of release notes, and functionality on latest looks the same.

[rus-ik]

+1.

[abdulhameedinfo2]

this is very basic thing, insomia should provide. it is very difficult currently to edit the variable same the id every time you add new item then you have go the colleciton, environment and bla bla to edit that id, so that you can use this id for other collection items. this is time consuming, please provide the open box to edit the value.

[ozkit]

+1
even Postman finally added this feature as popup, it's your turn, Insomnia

[mathisgauthey]

+1, we need to be able to have for instance an id that would be a variable but we also need to be able to quick edit that variable. Maybe adding an edit form in the middle between the Environment Variable and the Live Preview

[king-11]

I am not sure why is this request closed but definitely a useful feature.

[stephen1274]

+1 for this too.

[mathisgauthey]

I created a discussion so that the issue could live on : #8423