-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Advanced Search in the Explorer: augment with filters/modifiers #1
Comments
@FluorescentHallucinogen this is a great idea! We're still working on handling arguments and input objects fully in the search and docs, but it's in active development. I'll pass your thought here on to @Jephuff who has been working on handling arguments in particular. |
What about GraphQL list (array) inputs? This is essential feature. See OneGraph/graphiql-explorer#10 (comment). 😉 |
Re "Search in descriptions". Sometimes user doesn't remember exactly the name of the field/argument, but remembers some keyword from its description. |
@FluorescentHallucinogen thanks for your thoughtful suggestion (both the argument adding and the search options). Per the advanced search options, currently we are thinking of expanding the search syntax to afford for use cases like arguments. But eventually we may add form based search options like your suggestion. We'll certainly keep this in mind as we progress! ✨ 🙇✨ |
Yeah, that's a really cool experience for filtering available fields! |
@FluorescentHallucinogen I've renamed this issue because we're on the cusp of landing exactly what you described with the arguments, so I figured we could refocus the rest of this issue on Search. |
Before (current):
After (proposed):
The text was updated successfully, but these errors were encountered: