Repository navigation
Don't assume () on end of method calls #687
Description
See here: https://youtu.be/O7TXamVRSbY?t=41m43s
Putting parens on the end of methods isn't always appropriate. Plus, if we remove these and handle them as a triggerCharacter, it might address the other issue we had with duplicated parens.
Activity
DanTup commentedon Mar 14, 2018
This might be worth tackling after signature information, since the best fix is going to be to totally remove
insertArgumentPlaceholdersand then add(as a commit character.DanTup commentedon Jul 26, 2018
The fix here is to turn off insertArgumentPlaceholders (and turn on completionCommitCharacters), but that's not perfect without signature help.
DanTup commentedon Aug 22, 2018
I'm considering this "kinda fixed".
If you turn off
insertArgumentPlaceholdersthen we won't ever do this. And if you turn on commit characters, then if you commit with(then you'll get your parens. It's not perfect because commit characters are frustrating due to VS Code's fuzzy matching, but that's another issue.