Insomnium is a fast local API testing tool that is privacy-focused and 100% local. For testing GraphQL, REST, WebSockets and gRPC. This is a fork of Kong/insomnia
MIT License
3.3k
stars
123
forks
source link
Environment editor sets last selected environment to active after editing #143
If my active workspace environment is somthing, lets say Staging, when I open the environment editor and I switch to modify another environment (such as the Base Environment), when I close the editor, I expect my active environment to remain to Staging.
Actual Behavior
When I exit the environment window, the active environment becomes the last selected environment in the environment editor window, whatever it is.
Reproduction Steps
Ensure you have more than one environment.
Select one of the environments in the workspace.
Open the environment editor.
In the editor, select a different environment.
Close the editor. The new active environment is the environment that was selected in the editor.
Is there an existing issue for this?
[X] I have searched the issue tracker for this problem.
Expected Behavior
If my active workspace environment is somthing, lets say Staging, when I open the environment editor and I switch to modify another environment (such as the Base Environment), when I close the editor, I expect my active environment to remain to Staging.
Actual Behavior
When I exit the environment window, the active environment becomes the last selected environment in the environment editor window, whatever it is.
Reproduction Steps
Is there an existing issue for this?
Additional Information
The same issue is opened on the Insomnia project : https://github.com/Kong/insomnia/issues/6449 and https://github.com/Kong/insomnia/issues/6360. The behavior applies not only to the base environment but to other sub-environments as well, as I've descrived above.
Insomnium Version
0.2.3-a
What operating system are you using?
Windows
Operating System Version
Windows 11
Installation method
scoop.sh
Last Known Working Insomnium version
No response