in the "generate code" panel. #2284

New issue

Open

opened 2026-03-16 23:51:03 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @KatyaGolyagina on GitHub (Feb 3, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5827

Is there an existing issue for this?

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

Platform

Web App

Browser

Chrome

Operating System

Windows

Bug Description

what happens

I use the variable <<$guid>> in a query with a database record. I want to see the value that will be generated within the interface. To do this:

specify the value <<$guid>> in the parameter of the query.
open the "generate code" panel.
find the generated value <<$guid>>.
execute the query and go to the database to verify the record.

Expected result:

The value <<$guid>> in the specific field of the database will match the generated value in the "generate code" panel.

Actual result:

A different generated value <<$guid>> is saved in the database, which was not present in the "generate code" panel.

Overall, the value <<$guid>>, according to the "generate code" panel, changes every time you, for example, switch between response tabs at the bottom. I would like a bit more control - or not such chaotic updates of the variable.

Deployment Type

Self-hosted (on-prem deployment)

Version

Hoppscotch v2025.9.2

Originally created by @KatyaGolyagina on GitHub (Feb 3, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5827 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Web App ### Browser Chrome ### Operating System Windows ### Bug Description ## what happens I use the variable <<$guid>> in a query with a database record. I want to see the value that will be generated within the interface. To do this: 1. specify the value <<$guid>> in the parameter of the query. 2. open the "generate code" panel. 3. find the generated value <<$guid>>. 4. execute the query and go to the database to verify the record. ## Expected result: The value <<$guid>> in the specific field of the database will match the generated value in the "generate code" panel. ## Actual result: A different generated value <<$guid>> is saved in the database, which was not present in the "generate code" panel. Overall, the value <<$guid>>, according to the "generate code" panel, changes every time you, for example, switch between response tabs at the bottom. I would like a bit more control - or not such chaotic updates of the variable. ### Deployment Type Self-hosted (on-prem deployment) ### Version Hoppscotch v2025.9.2

kerem added the

bug

need testing

labels

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

kerem commented

2026-03-16 23:51:14 +03:00

Author

Owner

@shuaixr commented on GitHub (Feb 5, 2026):

I think generate code being inconsistent is acceptable, but History should store the actual resolved values used in the request (<<$guid>>) to make replaying requests easier.
If this makes sense, I am happy to discuss and fix for this.

@shuaixr commented on GitHub (Feb 5, 2026): I think generate code being inconsistent is acceptable, but History should store the actual resolved values used in the request (<<$guid>>) to make replaying requests easier. If this makes sense, I am happy to discuss and fix for this.

kerem referenced this issue

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

[PR #2284] [CLOSED] chore(deps): bump @codemirror/autocomplete from 0.19.15 to 0.20.0 #3701