Conversation
Previously, dot-prefixed completions like `xarg.x` would show irrelevant global completions when the prefix type could not be resolved. Now, completions are disabled entirely in such cases, returning no results. This provides a cleaner user experience by not showing unrelated suggestions. Property completions for non-module values may be added in the future. Fixes #389
|
Thanks for the fix!
Out of curiosity, when can the prefix type be resolved? I haven't been able to find any case that JETLS was able to tell me the fields of a local variable or argument yet. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #395 +/- ##
==========================================
+ Coverage 65.51% 65.53% +0.02%
==========================================
Files 44 44
Lines 4944 4947 +3
==========================================
+ Hits 3239 3242 +3
Misses 1705 1705
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The current implementation of However, by utilizing the |
Previously, dot-prefixed completions like
xarg.xwould show irrelevantglobal completions when the prefix type could not be resolved.
For now, let's just disable completions entirely in such cases, to
provide a cleaner user experience by not showing unrelated suggestions.
Property completions for non-module values may be added in the future.
Fixes #389