You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In the previous versions of cube and its playground, I was able to construct my GraphQL queries by typing in the editor. This seems to now be removed, which is frustrating given my usual workflow now has been disrupted. I did find that we can type into some obscure pop up, but this is far less usable than before because now its just a RTB instead of giving us the autocomplete features too.
Describe the solution you'd like
I'd like to be able to type out the query again as I like to have fine grained control over how and where my query params etc are used.
Describe alternatives you've considered
Previous version of the playground had this feature.
Additional context
N/A
edit: added extra info
The text was updated successfully, but these errors were encountered:
To add, I also find it unpleasent to have much less control over how I want to prepare my queries. I can't easily add a custom limit without having to use some odd work arounds, and there are some performance issues when trying to use large datasets.
Is there no option to revert to the 1.0 of the playground? This is pretty unworkable especially for query validation and sanity checks during our development experience
Is your feature request related to a problem? Please describe.
In the previous versions of cube and its playground, I was able to construct my GraphQL queries by typing in the editor. This seems to now be removed, which is frustrating given my usual workflow now has been disrupted. I did find that we can type into some obscure pop up, but this is far less usable than before because now its just a RTB instead of giving us the autocomplete features too.
Describe the solution you'd like
I'd like to be able to type out the query again as I like to have fine grained control over how and where my query params etc are used.
Describe alternatives you've considered
Previous version of the playground had this feature.
Additional context
N/A
edit: added extra info
The text was updated successfully, but these errors were encountered: