starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #4777] [feature]: search request by url #1794

New issue

Closed

opened 2026-03-16 21:45:40 +03:00 by kerem · 5 comments

kerem commented

2026-03-16 21:45:40 +03:00

Owner

Originally created by @cs12110 on GitHub (Feb 21, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4777

Is there an existing issue for this?

I have searched the existing issues

Summary

Can hoppscotch support search by request url?

If I got a request on collection:

name: my-request
url: https://a.com/b/c

Can we search this request by just using a part of url: b/c?

Why should this be worked on?

just want to find the target request quickly.

Originally created by @cs12110 on GitHub (Feb 21, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4777 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Can hoppscotch support search by request url? <img width="360" alt="Image" src="https://github.com/user-attachments/assets/2904405e-e5bb-4c1a-984b-6c9d594d6b30" /> If I got a request on collection: - name: my-request - url: https://a.com/b/c Can we search this request by just using a part of url: `b/c`? ### Why should this be worked on? just want to find the target request quickly.

kerem

2026-03-16 21:45:40 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 21:45:56 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Apr 3, 2025):

Hi, the latest release adds the ability to search requests via the endpoint under the personal workspace. Please feel free to let us know if you have any feedback.

@jamesgeorge007 commented on GitHub (Apr 3, 2025): Hi, the latest release adds the ability to search requests via the endpoint under the personal workspace. Please feel free to let us know if you have any feedback.

kerem commented

2026-03-16 21:46:02 +03:00

Author

Owner

@cs12110 commented on GitHub (Apr 8, 2025):

Hi, the latest release adds the ability to search requests via the endpoint under the personal workspace. Please feel free to let us know if you have any feedback.

On v25.3.0 add this feature, right? On the app, I haven't find the setting you describe. Is there anything I missing?

@cs12110 commented on GitHub (Apr 8, 2025): > Hi, the latest release adds the ability to search requests via the endpoint under the personal workspace. Please feel free to let us know if you have any feedback. On v25.3.0 add this feature, right? On the app, I haven't find the setting you describe. Is there anything I missing?

kerem commented

2026-03-16 21:46:07 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Jun 10, 2025):

Sorry for the delayed response. This feature is enabled by default in the personal workspace and does not require any specific setting. You can now search using parts of an endpoint as well as the request name. Please note that, at present, search is limited to a depth of 2 in this context.

@jamesgeorge007 commented on GitHub (Jun 10, 2025): Sorry for the delayed response. This feature is enabled by default in the personal workspace and does not require any specific setting. You can now search using parts of an endpoint as well as the request name. Please note that, at present, search is limited to a depth of `2` in this context.

kerem commented

2026-03-16 21:46:12 +03:00

Author

Owner

@cs12110 commented on GitHub (Jun 30, 2025):

Sorry for the delayed response. This feature is enabled by default in the personal workspace and does not require any specific setting. You can now search using parts of an endpoint as well as the request name. Please note that, at present, search is limited to a depth of 2 in this context.

Thanks for that response. But I don't know what is the search is limited to a depth of 2 in this context?

For example, I got an request url like :'a/b/c/d'. Only can search by c/d?

@cs12110 commented on GitHub (Jun 30, 2025): > Sorry for the delayed response. This feature is enabled by default in the personal workspace and does not require any specific setting. You can now search using parts of an endpoint as well as the request name. Please note that, at present, search is limited to a depth of `2` in this context. Thanks for that response. But I don't know what is the `search is limited to a depth of 2 in this context`? For example, I got an request url like :'a/b/c/d'. Only can search by `c/d`?

kerem commented

2026-03-16 21:46:17 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Jul 31, 2025):

What I meant was that, as shown in the screenshots, searching for req1 works because it's within two levels under the collection (col-1 > fold-1 > req1), whereas req2 doesn't show up since it's nested deeper (col-1 > fold-1 > fold-2 > req2).

Currently, the search is limited to a depth of 2 levels from the collection root.

@jamesgeorge007 commented on GitHub (Jul 31, 2025): What I meant was that, as shown in the screenshots, searching for `req1` works because it's within two levels under the collection (`col-1` > `fold-1` > `req1`), whereas `req2` doesn't show up since it's nested deeper (`col-1` > `fold-1` > `fold-2` > `req2`). Currently, the search is limited to a depth of `2` levels from the collection root. <img width="305" height="302" alt="Image" src="https://github.com/user-attachments/assets/5d590ae7-eee7-4573-939b-c971eec9ac60" /> <br /> <img width="479" height="309" alt="Image" src="https://github.com/user-attachments/assets/41724663-dc2b-4e3a-baef-941c5964e758" />

kerem referenced this issue

2026-03-17 01:06:26 +03:00

[PR #1794] [MERGED] Update korean translation #3498