starred/hoppscotch

Fork 0

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

[GH-ISSUE #2132] [bug]: Save option overrides the request name #716

New issue

Closed

opened 2026-03-16 16:50:39 +03:00 by kerem · 6 comments

kerem commented

2026-03-16 16:50:39 +03:00

Owner

Originally created by @kyteinsky on GitHub (Feb 25, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2132

Is there an existing issue for this?

I have searched the existing issues

Current behavior

What I've been going through:

When I have a REST request saved in a collection with a certain name xyz, and I change some parameters of the request and then save it again the name of the request inside the collection is changed to Untitled request.

What I expected to happen:

The request should've been saved with the same name (xyz).

Steps to reproduce

Import a request using cURL
Save a REST request with a name other than Untitled request
Change the request
Save it again

Environment

Production

Version

Local

Originally created by @kyteinsky on GitHub (Feb 25, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2132 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior ##### What I've been going through: When I have a REST request saved in a collection with a certain name `xyz`, and I change some parameters of the request and then save it again the name of the request inside the collection is changed to `Untitled request`. ##### What I expected to happen: The request should've been saved with the same name (`xyz`). ### Steps to reproduce 1. Import a request using cURL 2. Save a REST request with a name other than `Untitled request` 3. Change the request 4. Save it again ### Environment Production ### Version Local

kerem

2026-03-16 16:50:39 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 16:50:56 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Feb 26, 2022):

Huh, I wasn't able to reproduce this on my end.

@liyasthomas ?

@AndrewBastin commented on GitHub (Feb 26, 2022): Huh, I wasn't able to reproduce this on my end. @liyasthomas ?

kerem commented

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

Author

Owner

@liyasthomas commented on GitHub (Feb 26, 2022):

Same here. Can't reproduce this issue.

I suppose user might've reset the request (CMD+I) which will reset the request name to Untitled request.

@liyasthomas commented on GitHub (Feb 26, 2022): Same here. Can't reproduce this issue. I suppose user might've reset the request (<kbd>CMD</kbd>+<kbd>I</kbd>) which will reset the request name to `Untitled request`.

kerem commented

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

Author

Owner

@kyteinsky commented on GitHub (Feb 26, 2022):

I suppose user might've reset the request (CMD+I) which will reset the request name to Untitled request.

Nope, I checked it again and am able to reproduce the issue. This name Untitled request comes from makeRESTRequest in curlparser.ts from the name key. I will upload a video after some time.

@kyteinsky commented on GitHub (Feb 26, 2022): > I suppose user might've reset the request (CMD+I) which will reset the request name to `Untitled request`. Nope, I checked it again and am able to reproduce the issue. This name `Untitled request` comes from `makeRESTRequest` in `curlparser.ts` from the name key. I will upload a video after some time.

kerem commented

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

Author

Owner

@kyteinsky commented on GitHub (Feb 27, 2022):

https://user-images.githubusercontent.com/20724224/155871257-8a32d5c6-07b2-4b67-b20e-fec41c94eb8d.mp4

@kyteinsky commented on GitHub (Feb 27, 2022): https://user-images.githubusercontent.com/20724224/155871257-8a32d5c6-07b2-4b67-b20e-fec41c94eb8d.mp4

kerem commented

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

Author

Owner

@AndrewBastin commented on GitHub (Feb 27, 2022):

Oh okay.

Now, to be honest, I have found many issues with the Curl Implementation after the PR was merged. We might have to work on a continuing PR to rethink and reorganize some bits. This time with stronger standards and testing implementation to reinforce things are working properly.

@AndrewBastin commented on GitHub (Feb 27, 2022): Oh okay. Now, to be honest, I have found many issues with the Curl Implementation after the PR was merged. We might have to work on a continuing PR to rethink and reorganize some bits. This time with stronger standards and testing implementation to reinforce things are working properly.

kerem commented

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

Author

Owner

@kyteinsky commented on GitHub (Feb 27, 2022):

I did test the curl parser extensively, but this definitely calls for thorough tests to be written.

With that aside, I don't believe this issue has to do anything with that PR. makeRESTRequest and setRESTRequest are causing this to happen. I need some more time to look through it.

@kyteinsky commented on GitHub (Feb 27, 2022): I did test the curl parser extensively, but this definitely calls for thorough tests to be written. With that aside, I don't believe this issue has to do anything with that PR. `makeRESTRequest` and `setRESTRequest` are causing this to happen. I need some more time to look through it.

kerem referenced this issue

2026-03-17 00:29:12 +03:00

[PR #716] [MERGED] Updated Simplified Chinese translation. #2812