starred/hoppscotch

Fork 0

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

[GH-ISSUE #5629] [bug]: Commented lines generate newlines in the effective request #2180

New issue

Open

opened 2026-03-16 23:29:36 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 23:29:36 +03:00

Owner

Originally created by @JohannesBe on GitHub (Nov 28, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5629

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

Windows

Bug Description

Commented out lines should not generate a new line in the effective JSON sent over the wire.

For instance, take this request:

{
    "ProjectNumber": "<<PROJNO>>",
    // "ProjectManager": 1,
    // "ParentProject": null,
    // "ParentProjectName": null,
    // "Jobgroup": 1,
    "Description": "<<PROJNO>>",
    // "CustomerID": null,
    // "CustomerCode": null,
    // "CustomerCountry": null,
    // "CustomerName": null,
    // "CustomerType": null,
    // "ProjectCostCenter": null,
    // "ProjectCostUnit": null,
    // "Assortment": null,
    // "AssortmentName": null,
    // ...
    // "Materials": null,
  }

Has as output request something the likes of ( I removed some blank lines, you get the point):

{
    "ProjectNumber": "CR250005319",
    
    
    
    
    "Description": "CR250005319",
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
  }

This is really annoying when printing the body on a web server!

Also related: #5502
The trailing comma issue is really annoying when debugging with commented out lines!
You have to change the last line every time you send something!

Deployment Type

Hoppscotch Cloud

Version

No response

Originally created by @JohannesBe on GitHub (Nov 28, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5629 ### 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 Windows ### Bug Description Commented out lines should not generate a new line in the effective JSON sent over the wire. For instance, take this request: ```json { "ProjectNumber": "<<PROJNO>>", // "ProjectManager": 1, // "ParentProject": null, // "ParentProjectName": null, // "Jobgroup": 1, "Description": "<<PROJNO>>", // "CustomerID": null, // "CustomerCode": null, // "CustomerCountry": null, // "CustomerName": null, // "CustomerType": null, // "ProjectCostCenter": null, // "ProjectCostUnit": null, // "Assortment": null, // "AssortmentName": null, // ... // "Materials": null, } ``` Has as output request something the likes of ( I removed some blank lines, you get the point): ```json { "ProjectNumber": "CR250005319", "Description": "CR250005319", } ``` This is really annoying when printing the body on a web server! Also related: #5502 The trailing comma issue is really annoying when debugging with commented out lines! You have to change the last line every time you send something! ### Deployment Type Hoppscotch Cloud ### Version _No response_

kerem added the

bug

need testing

labels

2026-03-16 23:29:36 +03:00

kerem commented

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

Author

Owner

@myeonbi commented on GitHub (Nov 28, 2025):

Hi, I’ve tested this on the Web version (https://hoppscotch.io/
) using a JSON Body with commented lines, and the problem still appears:

Commented lines are removed from the request, but empty lines remain in the effective JSON sent over the wire.

This confirms that the issue (#5629) is still present.

I’d like to try fixing this. Could I be assigned to this issue?

Thanks!

@myeonbi commented on GitHub (Nov 28, 2025): Hi, I’ve tested this on the Web version (https://hoppscotch.io/ ) using a JSON Body with commented lines, and the problem still appears: Commented lines are removed from the request, but empty lines remain in the effective JSON sent over the wire. This confirms that the issue (#5629) is still present. I’d like to try fixing this. Could I be assigned to this issue? Thanks!

kerem commented

2026-03-16 23:29:52 +03:00

Author

Owner

@JohannesBe commented on GitHub (Dec 1, 2025):

Unfortunately, I cannot assign people, so we'll have to wait for a repo maintainer to do that :)

@JohannesBe commented on GitHub (Dec 1, 2025): Unfortunately, I cannot assign people, so we'll have to wait for a repo maintainer to do that :)

kerem referenced this issue

2026-03-17 01:15:29 +03:00

[PR #2180] [CLOSED] chore(deps-dev): bump @graphql-codegen/typescript from 2.4.7 to 2.4.8 #3661