starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 08:45:58 +03:00

[GH-ISSUE #1188] Add search (live filter?) box for GraphQL schema panel #407

New issue

Closed

opened 2026-03-16 15:09:18 +03:00 by kerem · 8 comments

kerem commented

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

Owner

Originally created by @Qix- on GitHub (Sep 25, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1188

Is your feature request related to a problem? Please describe.

The schema fetching in Hoppscotch is very helpful and (mostly) well laid-out. However, it appears to be using a virtual list of some sort and thus isn't ctrl+f searchable, making large schemas incredibly hard to traverse.

This, paired with the fact it can't be resized (it's a tiny sliver for me) and that clicking types and whatnot doesn't seem to scroll to the appropriate positions, makes it for kind of a clunky experience - especially when the API in question doesn't provide formal docs and instead simply points to the in-schema documentation.

Describe the solution you'd like

Basically this.

Describe alternatives you've considered

Nothing really, feels like this is a core feature that'd be abundantly useful.

Alternatively, a tree-like viewer instead of a long virtual list, where items can be expanded to include documentation notes and whanot (collapsed by default).

Additional context

Only appears to be missing for GraphQL. The component in the screenshot is just hacked in, copied from another tab.

Originally created by @Qix- on GitHub (Sep 25, 2020). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1188 **Is your feature request related to a problem? Please describe.** The schema fetching in Hoppscotch is very helpful and (mostly) well laid-out. However, it appears to be using a virtual list of some sort and thus isn't ctrl+f searchable, making large schemas incredibly hard to traverse. This, paired with the fact it can't be resized (it's a tiny sliver for me) and that clicking types and whatnot doesn't seem to scroll to the appropriate positions, makes it for kind of a clunky experience - especially when the API in question doesn't provide formal docs and instead simply points to the in-schema documentation. **Describe the solution you'd like** Basically this. ![image](https://user-images.githubusercontent.com/885648/94298672-d005a780-ff66-11ea-8d5b-d32d1311eafb.png) **Describe alternatives you've considered** Nothing really, feels like this is a core feature that'd be abundantly useful. Alternatively, a tree-like viewer instead of a long virtual list, where items can be expanded to include documentation notes and whanot (collapsed by default). **Additional context** Only appears to be missing for GraphQL. The component in the screenshot is just hacked in, copied from another tab.

kerem

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

closed this issue
added the
feature

core

hacktoberfest
labels

kerem commented

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

Author

Owner

@liyasthomas commented on GitHub (Sep 25, 2020):

Thanks for reporting your pain points regarding GraphQL page. We're working on an overhaul on GraphQL page and hoping to bring the best experience. Will use this issue as a base to track it's progress.

@liyasthomas commented on GitHub (Sep 25, 2020): Thanks for reporting your pain points regarding GraphQL page. We're working on an overhaul on GraphQL page and hoping to bring the best experience. Will use this issue as a base to track it's progress.

kerem commented

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

Author

Owner

@AndrewBastin commented on GitHub (Sep 27, 2020):

I think this will be good for Hacktoberfest as I am preoccupied with working on the Teams backend.

The implementation is pretty trivial actually.

Anyone interested can ping me (on Discord or Telegram group or here) if you need any pointers.

@AndrewBastin commented on GitHub (Sep 27, 2020): I think this will be good for Hacktoberfest as I am preoccupied with working on the Teams backend. The implementation is pretty trivial actually. Anyone interested can ping me (on Discord or Telegram group or here) if you need any pointers.

kerem commented

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

Author

Owner

@LeoMartinDev commented on GitHub (Oct 3, 2020):

I'll give it a try 👌

@LeoMartinDev commented on GitHub (Oct 3, 2020): I'll give it a try 👌

kerem commented

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

Author

Owner

@LeoMartinDev commented on GitHub (Oct 3, 2020):

I'm wondering, should it filter only on fieldName ? Maybe we could also search in the description, not sure about this

@LeoMartinDev commented on GitHub (Oct 3, 2020): I'm wondering, should it filter only on `fieldName` ? Maybe we could also search in the description, not sure about this

kerem commented

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

Author

Owner

@Qix- commented on GitHub (Oct 3, 2020):

Being able to fuzzy search for any of the content would be groundbreaking. Some of the schemas that get imported are massive and it's not always clear what the field name will be.

Just my $0.02.

@Qix- commented on GitHub (Oct 3, 2020): Being able to fuzzy search for any of the content would be groundbreaking. Some of the schemas that get imported are _massive_ and it's not always clear what the field name will be. Just my $0.02.

kerem commented

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

Author

Owner

@LeoMartinDev commented on GitHub (Oct 3, 2020):

Being able to fuzzy search for any of the content would be groundbreaking. Some of the schemas that get imported are massive and it's not always clear what the field name will be.

Just my $0.02.

You mean, including mutations args, fields types, etc.. ? Got something working, filtering on description & field/mutation/type name

@LeoMartinDev commented on GitHub (Oct 3, 2020): > Being able to fuzzy search for any of the content would be groundbreaking. Some of the schemas that get imported are _massive_ and it's not always clear what the field name will be. > > Just my $0.02. You mean, including mutations args, fields types, etc.. ? Got something working, filtering on description & field/mutation/type name

kerem commented

2026-03-16 15:10:05 +03:00

Author

Owner

@Qix- commented on GitHub (Oct 3, 2020):

Yeah, basically any part of the spec that is returned would be searchable in theory - within reason, of course.

@Qix- commented on GitHub (Oct 3, 2020): Yeah, basically any part of the spec that is returned would be searchable in theory - within reason, of course.

kerem commented

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

Author

Owner

@LeoMartinDev commented on GitHub (Oct 3, 2020):

Yeah, basically any part of the spec that is returned would be searchable in theory - within reason, of course.

For now it searches in name and description but I made it easy to add more keys to search in

@LeoMartinDev commented on GitHub (Oct 3, 2020): > Yeah, basically any part of the spec that is returned would be searchable in theory - within reason, of course. For now it searches in `name` and `description` but I made it easy to add more keys to search in

kerem referenced this issue

2026-03-17 00:17:51 +03:00

[PR #407] [MERGED] ⬆️ Bump @nuxtjs/google-analytics from 2.2.1 to 2.2.2 #2610

kerem referenced this issue

2026-03-17 00:18:08 +03:00

[PR #424] [MERGED] Even #2615