starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #5754] [bug]: Switching Environments does not update Current #2245

New issue

Open

opened 2026-03-16 23:42:47 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 23:42:47 +03:00

Owner

Originally created by @edmound-hubbard-enverus on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5754

Originally assigned to: @Fran2007 on GitHub.

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Desktop App

Browser

Chrome

Operating System

macOS

Bug Description

Path: /documentation/features/environments

Documentation mentions the 'Current' should change when the Environment becomes active. This does not happen. When you select environment the initial values are set, but when you make any API calls it refers to 'Current'. Need to edit and select 'Replace all Current with Initial'.

Deployment Type

Hoppscotch Cloud

Version

No response

Originally created by @edmound-hubbard-enverus on GitHub (Jan 6, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5754 Originally assigned to: @Fran2007 on GitHub. ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Desktop App ### Browser Chrome ### Operating System macOS ### Bug Description Path: /documentation/features/environments Documentation mentions the 'Current' should change when the Environment becomes active. This does not happen. When you select environment the initial values are set, but when you make any API calls it refers to 'Current'. Need to edit and select 'Replace all Current with Initial'. <img width="1108" height="195" alt="Image" src="https://github.com/user-attachments/assets/a5c0bd95-364e-4520-a015-7d8706d41df9" /> ### Deployment Type Hoppscotch Cloud ### Version _No response_

kerem added the

bug

need testing

labels

2026-03-16 23:42:47 +03:00

kerem commented

2026-03-16 23:42:58 +03:00

Author

Owner

@Fran2007 commented on GitHub (Jan 7, 2026):

Hi, i'd like to work on this issue. Let me know if i can take it.

@Fran2007 commented on GitHub (Jan 7, 2026): Hi, i'd like to work on this issue. Let me know if i can take it.

kerem commented

2026-03-16 23:43:03 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 7, 2026):

@Fran2007 you can pick this up.

@liyasthomas commented on GitHub (Jan 7, 2026): @Fran2007 you can pick this up.

kerem commented

2026-03-16 23:43:08 +03:00

Author

Owner

@Fran2007 commented on GitHub (Jan 7, 2026):

Hi @liyasthomas, thanks for assigning me this issue.

I've opened PR #5756 which addresses the environment synchronization problem by keeping the selected environment index in sync with CurrentValueService.

Please let me know if any additional changes or tests are needed. Happy to iterate on it.

@Fran2007 commented on GitHub (Jan 7, 2026): Hi @liyasthomas, thanks for assigning me this issue. I've opened PR #5756 which addresses the environment synchronization problem by keeping the selected environment index in sync with `CurrentValueService`. Please let me know if any additional changes or tests are needed. Happy to iterate on it.

kerem commented

2026-03-16 23:43:13 +03:00

Author

Owner

@nivedin commented on GitHub (Jan 19, 2026):

@edmound-hubbard-enverus Thanks for opening the issue, and sorry for the delayed response from my end. We need a few more details regarding the bug you mentioned.

Documentation mentions that ‘Current’ should change when the environment becomes active. This does not happen. When you select an environment, the initial values are set, but when you make any API calls it refers to ‘Current’. You need to edit and select ‘Replace all Current with Initial’.

The Current value is used at runtime when a request is executed, and it falls back to the Initial value only if the Current value is empty. Each environment has its own set of variables and associated Current values. So when we toggle the selected environment, the Current value is auto-populated if it has already been set previously.

Could you please check if this clarifies the issue? If not, kindly attach a screen recording of the behavior you’re seeing so we can better understand the problem.

@nivedin commented on GitHub (Jan 19, 2026): @edmound-hubbard-enverus Thanks for opening the issue, and sorry for the delayed response from my end. We need a few more details regarding the bug you mentioned. > Documentation mentions that ‘Current’ should change when the environment becomes active. This does not happen. When you select an environment, the initial values are set, but when you make any API calls it refers to ‘Current’. You need to edit and select ‘Replace all Current with Initial’. The Current value is used at runtime when a request is executed, and it falls back to the Initial value only if the Current value is empty. Each environment has its own set of variables and associated Current values. So when we toggle the selected environment, the Current value is auto-populated if it has already been set previously. Could you please check if this clarifies the issue? If not, kindly attach a screen recording of the behavior you’re seeing so we can better understand the problem.

kerem referenced this issue

2026-03-17 01:17:08 +03:00

[PR #2245] [CLOSED] refactor: migrate from options api to script setup with ts #3695