Autocomplete makes aliasing quite difficult

[mike-marcacci]

If there is a similarly spelled field, is is impossible to type out an alias. For example, if I have root query fields node and field2 it isn't possible to alias one as foo: node(id: "xxx") because typing the "f" in "foo" autocompletes to "field2".

The only way to get the correct field is either with some typing gymnastics (starting to type "xxxfoo" then removing the "xxx") or copy-and-paste from another editor.

At the very least it should be possible to switch off autocomplete, while keeping the autosuggest functionality.

[imolorhe]

@mike-marcacci 😂 "typing gymnastics".. Lmao! Sorry to hear that. We had a debate about that sometime ago, and it seems this settles that debate. I'd make the necessary changes to make it wait for you to select the autocomplete, even if it's the only option available. 😊

Cc @lon-io

[imolorhe]

@mike-marcacci By the way, any other usability issues you find, I'd be happy to work on. 😁

[mike-marcacci]

Wonderful! 😁 Thanks for the great plugin, BTW. It's really saved me when working offline, since graphiql is too large to embed in an app's source, and referencing it precompiled from a CDN only works over a network. It's nice to have a proper graphql UI where it belongs – on my system.

[imolorhe]

Yay!! 😁 Glad to hear that it's useful.

[imolorhe]

@mike-marcacci So I'm curious, on what platform do you use Altair? The chrome extension or the desktop app?

[mike-marcacci]

I only use the chrome extension. I actually didn't even know that there was a standalone app, since I found it in the chrome extension registry first and never looked back!