- My goal: Improve the Query library
- Issue: I have used the Query library recently and bumped into issues, this is a general feedback
Hi,
I have been trying to use the Query library but there are a few problems I encountered or expectations that become false.
Accessibility:
- To use a query library request, I have to create a query [any] then modify it and change the type to query library. It should probably be proposed in the choices.
Organization:
- A query library is a library thus supposed to grow, but there are no folders or similar.
- I expected the queries to be below the resources it is referring to
- An import of an OpenAPI spec would be a perfect addition.
The variables:
- The variables are shown as “just a variable” and came with the expectation like with other tools to be able to test the query. This felt very right as normal queries can’t be tested without making some shenanigans.
- It happened to be the default value of the variable.
- The values used in the query are meaningless as they have to be replicated in the client query; Maybe set the “default” to be the value set in the query on the left and leave “variables” to be the test variables?
- It proposes but shows an error when using sensible defaults like
{{ current_user.fullName }}
Note the additional data used here is necessary yet useless without being also set in the user of the query.
The Additional Data:
- When using the query, we do not see the valid additional data, yet it has to be set or it is reporting
undefined. - The auto-completion is broken
- The additional data usage reports “incorrect” (see the yellow line below the additional data)
- Both problems would be solved if the additional would be available only in the final query (in the user query) instead of the query library.
Please let me know if there is more information required to improve the query library;