Simple feature (for those who know the codebase better than I). This would make suggestions hidden while typing and wait for a user pause of chosen time.
Main goals
The primary goal is to not show information when it isn't needed (or wanted).
Most of the information displayed is never read (only on screen briefly between keystrokes), and what is read is usually done so during a pause.
Subjectively, things that blink very quickly -- like with every keystroke -- are not enjoyable.
Flow state is easier when there's less interruptions.
Having to ignore interruptions contributes to mental fatigue
Blinking things do not create a relaxed environment, something which can be very nice when low on energy or deep in thought.
How it would work:
user sets the show_completions_on_input to something representing a millisecond delay (number, string, w/e)
user begins typing, no completions are shown
user continues typing, no completions are shown
user stops typing for the millisecond delay, completions are shown
user continues typing, completions disappear until the next pause
user finishes what they were typing (whitespace, semi-colon, etc) or selects a completion, the completion overlay goes away
The I find most debatable about this suggestion:
UX question: Should the completions disappear when someone starts typing again? Does this require more than one setting to give proper control? If so, is it worth adding an extra setting?
IMO, I don't want to see anything but what I'm typing while I'm typing. I would likely set my pause in the range of 300-600ms.
If applicable, add mockups / screenshots to help present your vision of the feature
Check for existing issues
Describe the feature
Simple feature (for those who know the codebase better than I). This would make suggestions hidden while typing and wait for a user pause of chosen time.
Main goals The primary goal is to not show information when it isn't needed (or wanted).
How it would work:
show_completions_on_input
to something representing a millisecond delay (number, string, w/e)The I find most debatable about this suggestion: UX question: Should the completions disappear when someone starts typing again? Does this require more than one setting to give proper control? If so, is it worth adding an extra setting?
IMO, I don't want to see anything but what I'm typing while I'm typing. I would likely set my pause in the range of 300-600ms.
If applicable, add mockups / screenshots to help present your vision of the feature