You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
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.
The same issue is opened on the Insomnia project : Kong/insomnia#6449 and Kong/insomnia#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
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 : Kong/insomnia#6449 and Kong/insomnia#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
The text was updated successfully, but these errors were encountered: