[GH-ISSUE #597] Parameter list not showing JSON object fields (force raw?) #215

Closed
opened 2026-03-16 14:05:44 +03:00 by kerem · 6 comments
Owner

Originally created by @leomp12 on GitHub (Feb 24, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/597

Originally assigned to: @leomp12 on GitHub.

Describe the bug
JSON body is not being properly parsed to parameter list, when raw input is disabled the body seems to be empty even with a valid object set.

I'm not really sure if it's a bug, Imho the best approach is just force raw input for application/json content type and hide the switch input (feature request ?).
I can give a try if you agree :bowtie:

To Reproduce
Steps to reproduce the behavior:

  1. As example, go to this request;
  2. Disable raw input if enabled;
  3. Any property is shown on parameter list;

Expected behavior
On provided example, I was expecting to see app_id, title and the other body object properties on parameter list, or just force raw input for application/json and then show JSON body as is (Imo it would be even better than fix parameter list behavior).

Screenshots
Screenshot_2020-02-24 Postwoman • A free, fast and beautiful API request builder(1)
Screenshot_2020-02-24 Postwoman • A free, fast and beautiful API request builder

Desktop (please complete the following information):

  • OS: Linux 5.5.5-arch1-1 (Arch Linux)
  • Browser: Firefox
  • Version: 73.0.1 (64-bit)

Smartphone (please complete the following information):
N/A

Additional context
N/A

Originally created by @leomp12 on GitHub (Feb 24, 2020). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/597 Originally assigned to: @leomp12 on GitHub. **Describe the bug** JSON body is not being properly parsed to _parameter list_, when _raw input_ is disabled the body seems to be empty even with a valid object set. > I'm not really sure if it's a bug, Imho the best approach is just force _raw input_ for `application/json` content type and hide the switch input (feature request ?). I can give a try if you agree :bowtie: **To Reproduce** Steps to reproduce the behavior: 1. As example, go to [this request](https://postwoman.io/?method=POST&url=https://api.e-com.plus/v1&path=/applications.json&contentType=application/json&headers=%5B%7B%22key%22:%22X-Store-ID%22,%22value%22:%221056%22%7D,%7B%22key%22:%22X-My-ID%22,%22value%22:%221234%22%7D,%7B%22key%22:%22X-Access-Token%22,%22value%22:%22123%22%7D%5D&rawParams=%7B%0A%20%20%22app_id%22:%209000,%0A%20%20%22title%22:%20%22My%20Awesome%20E-Com%20Plus%20App%22,%0A%20%20%22slug%22:%20%22my-awesome-ecom-plus-app%22,%0A%20%20%22type%22:%20%22external%22,%0A%20%20%22state%22:%20%22active%22,%0A%20%20%22authentication%22:%20true,%0A%20%20%22modules%22:%20%7B%7D,%0A%20%20%22auth_scope%22:%20%7B%0A%20%20%20%20%22stores/me%22:%20%5B%0A%20%20%20%20%20%20%22GET%22%0A%20%20%20%20%5D,%0A%20%20%20%20%22procedures%22:%20%5B%0A%20%20%20%20%20%20%22POST%22%0A%20%20%20%20%5D,%0A%20%20%20%20%22products%22:%20%5B%5D,%0A%20%20%20%20%22brands%22:%20%5B%5D,%0A%20%20%20%20%22categories%22:%20%5B%5D,%0A%20%20%20%20%22customers%22:%20%5B%5D,%0A%20%20%20%20%22orders%22:%20%5B%5D,%0A%20%20%20%20%22carts%22:%20%5B%5D,%0A%20%20%20%20%22orders/fulfillments%22:%20%5B%5D,%0A%20%20%20%20%22orders/payments_history%22:%20%5B%5D,%0A%20%20%20%20%22products/quantity%22:%20%5B%5D,%0A%20%20%20%20%22products/variations/quantity%22:%20%5B%5D,%0A%20%20%20%20%22products/price%22:%20%5B%5D,%0A%20%20%20%20%22products/variations/price%22:%20%5B%5D%0A%20%20%7D,%0A%20%20%22auth_callback_uri%22:%20%22https://us-central1-ecom-app-boilerplate.cloudfunctions.net/app/ecom/auth-callback%22,%0A%20%20%22version%22:%20%221.0.0%22%0A%7D); 2. Disable _raw input_ if enabled; 3. Any property is shown on _parameter list_; **Expected behavior** On provided example, I was expecting to see `app_id`, `title` and the other body object properties on _parameter list_, or just force _raw input_ for `application/json` and then show JSON body as is (Imo it would be even better than fix parameter list behavior). **Screenshots** ![Screenshot_2020-02-24 Postwoman • A free, fast and beautiful API request builder(1)](https://user-images.githubusercontent.com/10326572/75189720-8ed9ba80-572d-11ea-9910-7f627935ddb9.png) ![Screenshot_2020-02-24 Postwoman • A free, fast and beautiful API request builder](https://user-images.githubusercontent.com/10326572/75189723-900ae780-572d-11ea-9936-5727e2c3cde7.png) **Desktop (please complete the following information):** - OS: Linux 5.5.5-arch1-1 (Arch Linux) - Browser: Firefox - Version: 73.0.1 (64-bit) **Smartphone (please complete the following information):** N/A **Additional context** N/A
kerem 2026-03-16 14:05:44 +03:00
  • closed this issue
  • added the
    feature
    label
Author
Owner

@liyasthomas commented on GitHub (Feb 24, 2020):

well, the raw parameter feature for payload enables us to send nested arrays, import JSON file contents etc. So I afraid we can't directly map the raw parameter objects to key -value pairs.

And regarding forcing whether key-value pair or raw parameters toggle, well this seems like a better option since even though the provided example request had raw parameters enabled, I was served with the default key-value pairs at first. I'd to manually toggle to raw parameters to see tje payload.

<!-- gh-comment-id:590588937 --> @liyasthomas commented on GitHub (Feb 24, 2020): well, the raw parameter feature for payload enables us to send nested arrays, import JSON file contents etc. So I afraid we can't directly map the raw parameter objects to key -value pairs. And regarding forcing whether key-value pair or raw parameters toggle, well this seems like a better option since even though the provided example request had raw parameters enabled, I was served with the default key-value pairs at first. I'd to manually toggle to raw parameters to see tje payload.
Author
Owner

@leomp12 commented on GitHub (Feb 24, 2020):

@liyasthomas great! You want me to give a try? If so, you can assign me to the issue.

<!-- gh-comment-id:590597152 --> @leomp12 commented on GitHub (Feb 24, 2020): @liyasthomas great! You want me to give a try? If so, you can assign me to the issue.
Author
Owner

@liyasthomas commented on GitHub (Feb 24, 2020):

sure! We'd love to have you onboard! Assigning this to you.

<!-- gh-comment-id:590604429 --> @liyasthomas commented on GitHub (Feb 24, 2020): sure! We'd love to have you onboard! Assigning this to you.
Author
Owner

@liyasthomas commented on GitHub (Mar 11, 2020):

@leomp12 how's the progress on this issue?

<!-- gh-comment-id:597423250 --> @liyasthomas commented on GitHub (Mar 11, 2020): @leomp12 how's the progress on this issue?
Author
Owner

@leomp12 commented on GitHub (Mar 11, 2020):

Hey @liyasthomas ,
I haven't had time yet, sorry 😞
I was planning to do it next week, probably on Monday or Tuesday, it's ok for you to wait?

<!-- gh-comment-id:597670512 --> @leomp12 commented on GitHub (Mar 11, 2020): Hey @liyasthomas , I haven't had time yet, sorry :disappointed: I was planning to do it next week, probably on Monday or Tuesday, it's ok for you to wait?
Author
Owner

@liyasthomas commented on GitHub (Mar 11, 2020):

yeah sure! ✌️💯

<!-- gh-comment-id:597670751 --> @liyasthomas commented on GitHub (Mar 11, 2020): yeah sure! ✌️💯
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#215
No description provided.