IntelliJ toggle TabNine result order to be before or after native autocompleteSee original GitHub issue
Been beta testing TabNine for a while and this is the summary of my experience so far. The codebase is GraphQL server, a React Frontend, a AWS CDK application and some MD and SQL.
In cases where there are no “native” suggestions, TabNine adds tremendous value. But to me there is a big difference in how positive and accurate TabNine completions over native IntelliJ symbol suggestions from the indexed-based autocompletion engine they have. The IntelliJ symbol is in a very large majority of cases more relevant when working directly on Types with symbols. So much so that TabNine feels like a nuisance since it’s never more accurate, and often fills the result list with suggestions that are redundant.
So my feature request as such is: Add a setting to keep IntelliJ native symbol suggestions, if they exist, above the TabNine suggestions, as an alternative to having TabNine always on top. This way, you can have the best of both worlds.
Disable TabNine suggestions from “Smart Type” completions. Intellij has two completion modes, “Basic” and “Smart Type”, which can be triggered with different key combinations:
As a developer, if I trigger the context-based SmartType completion, I want that context-based Type completion over anything else.
Here it’s suggesting strings that dont exist on the type at all.
Here I want to access
secret but the TabNine completion is in the way, disallowing me from completing automatically and forcing list navigation.
- Created 3 years ago
- Comments:23 (2 by maintainers)
Top GitHub Comments
@boaz-codota Can you please reopen this issue? If you’re not going to, can you give us an explanation why? I think you can see from the comments, that this is a pain point for a lot of people, including myself. Thanks
“And enterprises of great pith and moment With this regard their currents turn awry, And lose the name of action”
@boaz-codota with the above workaround, suggestions are still on top or native most of the time, so it is not clear what is awesome and why the ticket was closed.