Sorry, something went wrong.
|
I personally like this, and I think at least the second part, attribute completion changes, should be added. |
Sorry, something went wrong.
Codecov ReportMerging #840 (0cc3b86) into main (d07a405) will decrease coverage by 0.19%. @@ Coverage Diff @@
## main #840 +/- ##
==========================================
- Coverage 67.95% 67.76% -0.20%
==========================================
Files 61 61
Lines 9144 9154 +10
==========================================
- Hits 6214 6203 -11
- Misses 2930 2951 +21
Continue to review full report at Codecov. Legend - Click here to learn more |
Sorry, something went wrong.
TLDR:
Sorry for the bad quality gifs. I should stop using GIPHY for this.
Native function completion
Current behavior: open parenthesis in suggestion and autofill. You have to type something after the paren before you can see the method signature.
My proposal: open AND close parens in suggestion, no parens in autofill. Now typing the open paren shows the method signature.
This might mess with some people's muscle memory since it changes what's autofilled.
Attributute completion
Current behavior: no parens in suggestion or autofill. You can't tell what is a method or otherwise.
My proposal: open close parens in suggestion, no parens in autofill. Very clear which attrs are methods.
Since this only changes the infobox, it shouldn't mess with anyone's muscle memory.
If this seems worth implementing, I'll need to fix some tests. Right now, tests expect matches that look like "math.cos" or "any(", but they'll be getting matches that look like "math.cos()" and "any()".
Also I'm not sure if I implemented this the best way. The way I did it, the actual match string is altered to have parens. Maybe it's better to leave the match as-is, but add parenthesis only on the front end. This would require some passing around of information. Feedback appreciated.