dom
July 1, 2020, 10:28pm
1
Anyone else having problems with autocomplete in GraphiQL? When pressing enter to go to a new line, the autocomplete eats the input, making for a very annoying experience.
Browser: Chrome
Relevant Prisma issue:
opened 03:25AM - 30 May 18 UTC
#### This issue pertains to the following package(s):
- [ ] GraphQL Playgroun… d - Electron App
- [ ] GraphQL Playground HTML
- [x] GraphQL Playground
- [x] GraphQL Playground Express Middleware
- [ ] GraphQL Playground Hapi Middleware
- [ ] GraphQL Playground Koa Middleware
- [ ] GraphQL Playground Lambda Middleware
#### What OS and OS version are you experiencing the issue(s) on?
n/a it's the browser based client
#### What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
"graphql-playground-middleware-express": "^1.6.2",
#### What is the expected behavior?
When I press enter, it should go to the next line.
#### What is the actual behavior?
Pressing enter gets eaten by the autocomplete. This forces the user to press enter twice.
#### What steps may we take to reproduce the behavior?
Have a schema and start typing. Let's say I'm typing something like:
```
{
users {
username
}
}
```
When I start typing `usern` it pops up the autocompletion. This is fine. But when I continue typing `ame<ENTER>` then the autocomplete eats the ENTER keypress and it doesn't go to the newline. I have to type `username<ENTER><ENTER>`.
This is annoying as it makes it so that what I type is not what appears.
I've also seen weird things where I type open brace and then type space but autocomplete also eats the space forcing me to go back and edit to add the space.
_Please provide a gif or image of the issue for a quicker response/fix._
(Doesn’t seem to happening on Brave + Ubuntu though
2 Likes
.)