starred/hoppscotch

Fork 0

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

[GH-ISSUE #1497] Address bar URL params do not update as expected #476

New issue

Closed

opened 2026-03-16 15:35:09 +03:00 by kerem · 5 comments

kerem commented

2026-03-16 15:35:09 +03:00

Owner

Originally created by @nelsontky on GitHub (Feb 19, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1497

Describe the bug
POST parameters do not update the URL params in the address bar as expected

To Reproduce
Steps to reproduce the behavior:

Create a new POST request.
Add a new parameter to the request body. (Non raw request body)
Set the key to some text.
Click on the value input field.
The address bar URL parameter does not update.
Type something in the param value input field.
The address bar URL finally updates.

Expected behavior
The address bar URL parameter should have updated to reflect the new key in step 5.

Video
https://user-images.githubusercontent.com/7272103/108542861-3e387580-731f-11eb-9bae-ef2b747586d2.mp4

Desktop (please complete the following information):

OS: Windows
Browser: Chrome
Version: Latest

Additional context
I could work on this too!

Originally created by @nelsontky on GitHub (Feb 19, 2021). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1497 **Describe the bug** `POST` parameters do not update the URL params in the address bar as expected **To Reproduce** Steps to reproduce the behavior: 1. Create a new `POST` request. 2. Add a new parameter to the request body. (Non raw request body) 3. Set the key to some text. 4. Click on the value input field. 5. The address bar URL parameter does not update. 6. Type something in the param value input field. 7. The address bar URL finally updates. **Expected behavior** The address bar URL parameter should have updated to reflect the new key in step 5. **Video** https://user-images.githubusercontent.com/7272103/108542861-3e387580-731f-11eb-9bae-ef2b747586d2.mp4 **Desktop (please complete the following information):** - OS: Windows - Browser: Chrome - Version: Latest **Additional context** I could work on this too!

kerem

2026-03-16 15:35:09 +03:00

closed this issue
added the
need testing
label

kerem commented

2026-03-16 15:35:25 +03:00

Author

Owner

@LeoMartinDev commented on GitHub (Mar 2, 2021):

I'll take a look

@LeoMartinDev commented on GitHub (Mar 2, 2021): I'll take a look

kerem commented

2026-03-16 15:35:30 +03:00

Author

Owner

@LeoMartinDev commented on GitHub (Mar 2, 2021):

Ok well, this code is super hard to read and there is too many entry points to the setRouteQueryState function (and a watcher) so I'm having a hard time fixing this issue. Maybe someone with more experience on this part of the project will be able to find what's wrong 💪

@LeoMartinDev commented on GitHub (Mar 2, 2021): Ok well, this code is super hard to read and there is too many entry points to the `setRouteQueryState` function (and a watcher) so I'm having a hard time fixing this issue. Maybe someone with more experience on this part of the project will be able to find what's wrong 💪

kerem commented

2026-03-16 15:35:35 +03:00

Author

Owner

@nelsontky commented on GitHub (Mar 2, 2021):

Ok well, this code is super hard to read and there is too many entry points to the setRouteQueryState function (and a watcher) so I'm having a hard time fixing this issue. Maybe someone with more experience on this code will be able to find what's wrong 💪

Ok I can probably can have a go at it tomorrow!

@nelsontky commented on GitHub (Mar 2, 2021): > Ok well, this code is super hard to read and there is too many entry points to the `setRouteQueryState` function (and a watcher) so I'm having a hard time fixing this issue. Maybe someone with more experience on this code will be able to find what's wrong 💪 Ok I can probably can have a go at it tomorrow!

kerem commented

2026-03-16 15:35:40 +03:00

Author

Owner

@JayceDugan commented on GitHub (Mar 16, 2021):

After reviewing the existing description, discussion and having a brief inspection, I do not believe there is an issue here as there may have been a slight misunderstanding with expectations that body parameters operate the same as query parameters in a HTTP request.

Request body parameters do not get appended to a URL in a HTTP request and are instead transmitted immediately after request header under the body options key.

Request query parameters are a set of parameters appended to the end of a URL which appears to be the expected outcome described by this issue.

The existing functionality of request body parameters and request query parameters both appear to be operating relatively as expected (I found a separate issue with request query parameters.).

Request body parameters are attached to the request body, and creating a new GET request and applying query parameters results in the parameters being appended to the request URL. (Though they are not appended correctly but that is a separate issue and requires a different issue write up.)

@nelsontky @LeoMartinDev

@JayceDugan commented on GitHub (Mar 16, 2021): After reviewing the existing description, discussion and having a brief inspection, I do not believe there is an issue here as there may have been a slight misunderstanding with expectations that `body parameters` operate the same as `query parameters` in a HTTP request. `Request body parameters` do **not** get appended to a URL in a HTTP request and are instead transmitted immediately after request header under the `body` options key. `Request query parameters` are a set of parameters appended to the end of a URL which appears to be the expected outcome described by this issue. The existing functionality of `request body parameters` and `request query parameters` both appear to be operating relatively as expected (I found a separate issue with request query parameters.). Request body parameters are attached to the `request body`, and creating a new `GET` request and applying `query parameters` results in the parameters being appended to the request URL. (Though they are not appended correctly but that is a separate issue and requires a different issue write up.) @nelsontky @LeoMartinDev

kerem commented

2026-03-16 15:35:45 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 13, 2021):

@nelsontky I can't reproduce this issue in hoppscotch.io anymore. Can you verify this error exists?

@liyasthomas commented on GitHub (Apr 13, 2021): @nelsontky I can't reproduce this issue in [hoppscotch.io](https://hoppscotch.io) anymore. Can you verify this error exists?

kerem referenced this issue

2026-03-16 17:56:12 +03:00

[GH-ISSUE #3022] [feature]: RFC 7591: Dynamic Client Registration #983

kerem referenced this issue

2026-03-17 00:19:46 +03:00

[PR #476] [MERGED] OAuth 2.0/OIDC Access Token Retrieval Support #2644

kerem referenced this issue

2026-03-17 00:20:02 +03:00

[PR #485] [MERGED] chore: Minor tweaks #2646

kerem referenced this issue

2026-03-17 00:20:02 +03:00

[PR #486] [MERGED] chore(oauth): Added method signatures as per JSDoc conventions #2649