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
I find very uncomfortable to have forced auto-pairing completion.
An example that makes me make mistakes and/or type more instead of less:
Step 1: Date.parse("2019-07-31T22:13:54.697Z")
Step 2: now I want to check it, so I go to the beginning of the line, and type isNaN( and after the first parenthesis, jay autocompletes for me the second, leaving me with: isNaN()Date.parse("2019-07-31T22:13:54.697Z")
Now I have to delete the bad closing parenthesis. Some times is even worst since I forget about the autocompletion and go to the end to add the second one, and press ENTER, just to notice syntax is wrong.
Another way this results uncomfortable is when you paste something which gets auto-paired, causing bad syntax again.
I would vote to completely remove the feature, since I find it's not useful at all, but a configuration option to disable it would be ok too.
The text was updated successfully, but these errors were encountered:
I find very uncomfortable to have forced auto-pairing completion.
An example that makes me make mistakes and/or type more instead of less:
Step 1:
Date.parse("2019-07-31T22:13:54.697Z")
Step 2: now I want to check it, so I go to the beginning of the line, and type
isNaN(
and after the first parenthesis, jay autocompletes for me the second, leaving me with:isNaN()Date.parse("2019-07-31T22:13:54.697Z")
Now I have to delete the bad closing parenthesis. Some times is even worst since I forget about the autocompletion and go to the end to add the second one, and press
ENTER
, just to notice syntax is wrong.Another way this results uncomfortable is when you paste something which gets auto-paired, causing bad syntax again.
I would vote to completely remove the feature, since I find it's not useful at all, but a configuration option to disable it would be ok too.
The text was updated successfully, but these errors were encountered: